Microsoft KB Archive/286257

= FIX: DBCC CHECKTABLE May Fail if Table has a Text/Image Column and Long Clustering Key =

Article ID: 286257

Article Last Modified on 3/14/2006

-

APPLIES TO


 * Microsoft SQL Server 7.0 Standard Edition

-



This article was previously published under Q286257



BUG #: 58222 (SQLBUG_70)



SYMPTOMS
When you execute a DBCC CHECKTABLE statement, the command may fail and the following error message occurs:

[Microsoft][ODBC SQL Server Driver][Named Pipes]ConnectionCheckForData (PeekNamedPipe).

[Microsoft][ODBC SQL Server Driver][Named Pipes]Connection broken.

The error message occurs only if the following conditions are true:


 * A DBCC CHECKTABLE statement is executed on a table.
 * There are text or image columns in the table.
 * The clustering key for the table is at least 400 bytes long.



WORKAROUND
To work around this problem:
 * 1) Script out all the objects from the affected database.
 * 2) Create a new database, and then execute the scripts from step 1 to create all the tables and other database objects.
 * 3) Use the bcp utility to copy the data out into flat files. Use the bcp utility to copy the data from the flat files into the scripted database that you created in step 2.
 * 4) Drop all the AUTO_CREATE_STATISTICS indexes from the new database.



STATUS
Microsoft has confirmed this to be a problem in SQL Server 7.0. This problem has been corrected in U.S. Service Pack 3 for Microsoft SQL Server 7.0. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

274799 INF: How to Obtain Service Pack 3 for Microsoft SQL Server 7.0 and Microsoft Data Engine (MSDE) 1.0

For more information, contact your primary support provider.

Keywords: kbbug kbfix KB286257

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.