Microsoft KB Archive/136440

{|
 * width="100%"|

FIX: Create Worktable for Oversized Table Can Stop the Server

 * }

Q136440

-

The information in this article applies to:


 * Microsoft SQL Server version 6.0

-

BUG# NT: 10083 (6.00)

SYMPTOMS
When you attempt to create a worktable for storing intermediate results on a query involving an ORDER BY or GROUP BY clause for an oversized table, it can cause a server access violation.

When you create a table with a row size more than 1962 bytes, SQL Server generates a warning that the row is oversized, yet still creates the table. Inserting data into the table will work fine, as long as the actual data being inserted is less than 1962 bytes.

When you SELECT the data out without an ORDER BY or GROUP BY clause, the rows are retrieved normally, since there is no worktable involved. If a worktable is involved for ORDER BY or GROUP BY, then the server stops; it generates an unhandled exception, resulting in a Dr. Watson log.

WORKAROUND
Ensure that the base table is not created to be larger than the maximum size of a row. Alternately, do not use ORDER BY or GROUP BY in SELECT statements that operate on oversized tables.

STATUS
Microsoft has confirmed this to be a problem in Microsoft SQL Server version 6.0. This problem was corrected in Service Pack 1 for SQL Server version 6.0. For more information, contact your primary support provider.

Additional query words: SQL6 oversized row kill

Keywords : kbprogramming

Issue type : kbbug

Technology : kbSQLServSearch kbAudDeveloper kbSQLServ600