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 - 2006-06-19 : 08:28:10
|
Paul writes "Hi, We have run the following command...DBCC CHECKDB ('db_name')... and 12'622 consistency errors were found (all on the same index on the same table).So next we ran...DBCC CHECKTABLE ('table_name', REPAIR_ALLOW_DATA_LOSS)... and this fixed SOME of the errors, but not all...12586 consistency errors in tableDoes anyone have any ideas?Just to confirm this is SQL Server 2000.I do have both of the results logs available if that would help.Many Thanks, Paul." |
|
nr
SQLTeam MVY
12543 Posts |
Posted - 2006-06-19 : 08:46:27
|
Try rebuilding the index.==========================================Cursors are useful if you don't know sql.DTS can be used in a similar way.Beer is not cold and it isn't fizzy. |
|
|
paulrandal
Yak with Vast SQL Skills
899 Posts |
Posted - 2006-06-19 : 13:08:55
|
I'm guessing this is a clustered index (because it didn't fix all errors), so Nigel's advice is incorrect.Don't just run repair - see my blog post on this for why not (https://blogs.msdn.com/sqlserverstorageengine/archive/2006/06/16/633645.aspx). Do you have any backups?Please re-run 'DBCC CHECKDB (dbname) WITH ALL_ERRORMSGS, NO_INFOMSGS' and post the results.Did anything out of the ordinary occur before this happened? (e.g. power failure). If not, have you done any digging to figure out what went wrong so you avoid it happening again?ThanksPaul RandalLead Program Manager, Microsoft SQL Server Storage Engine + SQL Express(Legalese: This posting is provided "AS IS" with no warranties, and confers no rights.) |
|
|
|
|
|