SQL Server Performance

dbcc checkdb integrity errors - what are errors and is a partial restore possible?

Discussion in 'ALL SQL SERVER QUESTIONS' started by Trev256b, Feb 21, 2012.

  1. Trev256b Member

    hi everyone - i have spotted the following errors when running dbcc checkdb on some databases: msg: 8966, 8921, 8909, 2533, 926, 5269, 824, 823.

    i suspect all databases are corrupt. i think the best way to resolve this is to restore from a previous backup, however, if i use a backup before the corruption we will lose too much data.
    1) can i do a partial restore to avoid losing too much data? if so how can this be done?
    2) if a partial restore is possible then should i restore a second database and manually import data from the newer corrupted database, or can i import uncorrupted data from a backup?

    3) Is there a list of all these database integrity errors in a handy reference document?
    4) If I don't restore the databases and leave the integrity errors, what will the result be? will the database still remain operational???????
  2. Hrishi_nk New Member

  3. Luis Martin Moderator

    Did you try any of this options?
    REPAIR_ALLOW_DATA_LOSS | REPAIR_FAST | REPAIR_REBUILD

Share This Page