September 24, 2010 at 4:00 am
This isn't a corrupt table, it's a corrupt database.
There's damage to some critical system table. This is not repairable in any way. CheckDB cannot repair the system tables as doing so may have unacceptable effects on the rest of the database.
Your only options here are:
1) Restore to a clean backup. If you have log backups dating from that clean backup you can restore without data loss. Otherwise accept that you will lose everything since that backup
2) Script all objects and export all data. Accept that some may fail because of the corruption. Recreate the database from what you can get out.
Take a look at this article. http://www.sqlservercentral.com/articles/65804/
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
Viewing post 1 (of 2 total)
You must be logged in to reply to this topic. Login to reply