Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
AskSQLTeam
Ask SQLTeam Question
0 Posts |
 Posted - 2002-04-21 : 22:26:42
|
| John writes "A DBCC CHECKTABLE was run and returned the following errors on sysindexes.Server: Msg 8964, Level 16, State 1, Line 1Table Corrupt: Object ID 2. The text, ntext, or image node at page (1:1241), slot 21, text ID 5525798912 is not referenced.Server: Msg 8965, Level 16, State 1, Line 1Table Corrupt: Object ID 2. The text, ntext, or image node at page (1:2875816), slot 0, text ID 5525798912 is referenced by page (1:1241), slot 21, but was not seen in the scan.DBCC results for 'sysindexes'.There are 1542 rows in 72 pages for object 'sysindexes'.CHECKTABLE found 0 allocation errors and 2 consistency errors in table 'sysindexes' (object ID 2).repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKTABLE.Any ideas on how to clean this up without having to export data to a identical database? " |
|
|
Nazim
A custom title
1408 Posts |
Posted - 2002-04-22 : 02:31:38
|
| i would suggest you to take a backup of the database and run dbcc checkdb with REPAIR_ALLOW_DATA_LOSS option.-------------------------------------------------------------- |
 |
|
|
AjarnMark
SQL Slashing Gunting Master
3246 Posts |
Posted - 2002-04-22 : 20:27:26
|
| Since your errors are on a system table I would suggest you think a long time before you run REPAIR_ALLOW_DATA_LOSS, and indeed, seriously consider exporting your data to a new database.From BOL: "Sysindexes contains one row for each index and table in the database."Edited by - AjarnMark on 04/22/2002 20:28:42 |
|
|
|
|
|
|
|
|
DBCC Checktable turned up table corruption errors on sysindexes