BUG: DBCC CHECKTABLE(SYSINDEXES) Causes SQL Server to Stop Responding (200337)
The information in this article applies to:
This article was previously published under Q200337
BUG #: 18478 (SQLBUG_65)
SYMPTOMS
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.
CAUSE
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.
STATUS
Microsoft has confirmed this to be a problem in SQL Server 6.5.
MORE INFORMATION
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.
| Modification Type: | Major | Last Reviewed: | 10/3/2003 |
|---|
| Keywords: | kbBug kbpending KB200337 |
|---|
|