BUG: DBCC CHECKTABLE(SYSINDEXES) Causes SQL Server to Stop RespondingID: Q200337
|
Executing DBCC CHECKTABLE(sysindexes) may cause SQL Server to stop responding when there is a row on an index page owned by sysindexes but that page does not actually exist.
The index page pointers in the index structure show a row that there is no page for. This can occur when the dropping of an index did not complete successfully.
Microsoft has confirmed this to be a problem in SQL Server version 6.5.
Because DBCC CHECKDB includes running DBCC CHECKTABLE(sysindexes), it may also cause SQL Server to stop responding. DBCC NEWALLOC may report error 2540, but you can remove these errors by running DBCC FIX_AL.
Additional query words: hang hangs hung
Keywords : kbbug6.50
Version : winnt:6.5
Platform : winnt
Issue type : kbbug
Last Reviewed: March 6, 1999