Posted by Taw on 12/08/07 08:31

On Dec 5, 8:54 pm, Erland Sommarskog <esq...@sommarskog.se> wrote:
> Taw (tawfiq.choudh...@grameenphone.com) writes:
> > The following query which used to run regularly is crashing the
> > server. The query is run on two tables which has aroung 60 million
> > records each.
>
> Does the entire server really crash, or is just the process terminated.
>
> > Of course the query can be broken up and optimized I am just
> > interested to know if any one has any clue why this is happening?
>
> As Greg said, the most likely reason is a bug in SQL Server. The other
> alternative is a hardware problem (bad memory, bad disk sector).
>
> If you open a case with Microsoft, they have a fix that addresses the
> bug. But it's more likely that you will arrive at a working query by
> tweaking in a bit, possibly using temp tables for intermediate storage.
>
> --
> Erland Sommarskog, SQL Server MVP, esq...@sommarskog.se
>
> Books Online for SQL Server 2005 athttp://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books...
> Books Online for SQL Server 2000 athttp://www.microsoft.com/sql/prodinfo/previousversions/books.mspx

Thanks to all for your support. Actually the table is corrupted.
Fortunately we still have the raw data and are reporocessing it.

[Back to original message]