several databses with consistency errors

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.

All Forums

General SQL Server Forums

Data Corruption Issues

several databses with consistency errors

Author

Topic

jpotucek
Constraint Violating Yak Guru

273 Posts

Posted - 2008-04-05 : 12:10:29

sql server 2000 .. harddrive problems resolved but now several of my datatbases have consistency errors.. lots of them.

best way to repair????????? need to get this resolved asap

paulrandal
Yak with Vast SQL Skills

899 Posts

Posted - 2008-04-05 : 13:22:33

You need to restore from your backups - go read my reply to your cross-post on sqlservercentral.com

Thanks

Paul Randal
Managing Director, SQLskills.com

steel
Posting Yak Master

107 Posts

Posted - 2008-04-24 : 06:12:46

quote:
Originally posted by jpotucek

sql server 2000 .. harddrive problems resolved but now several of my datatbases have consistency errors.. lots of them.

best way to repair????????? need to get this resolved asap

U can use repair rebuild option of the dbcc checkdb ,but this will fail in case of the system tables i.e if error is in system tables.
also show the errors i.e. output of dbcc.

paulrandal
Yak with Vast SQL Skills

899 Posts

Posted - 2008-04-24 : 07:59:29

quote:
Originally posted by steel

quote:
Originally posted by jpotucek

sql server 2000 .. harddrive problems resolved but now several of my datatbases have consistency errors.. lots of them.

best way to repair????????? need to get this resolved asap

U can use repair rebuild option of the dbcc checkdb ,but this will fail in case of the system tables i.e if error is in system tables.
also show the errors i.e. output of dbcc.

Repair is not a good suggestion unless there are no backups.

REPAIR_REBUILD will do nothing except rebuild any corrupt non-clustered indexes, so is usually pretty pointless to run - you'd be better manually rebuilding the indexes and avoiding going into SINGLE_USER mode.

Usually REPAIR_ALLOW_DATA_LOSS is the way to go if there are no backups, and that will not be able to repair everything (including skipping critical system tables).

See CHECKDB From Every Angle category on my blog for more details.

Thanks

Paul Randal
SQL Server MVP, Managing Director, SQLskills.com

Subscribe to SQLTeam.com

SQLTeam.com Articles via RSS

SQLTeam.com Weblog via RSS

- Advertisement -

Resources