database in suspect mode

  • Hi

    i tried to put the database in emergency

    and then put into single user mode and ran dbcc check db with repair_allow_data_loss command but i am getting below error.... can any one help

    Msg 7987, Level 16, State 1, Line 1

    System table pre-checks: Object ID 3 has chain linkage mismatch. (1:5177)->next = (1:3277), but (1:3277)->prev = (1:1289). Check statement terminated due to unrepairable error.

  • m.rajesh.uk (6/12/2013)


    Check statement terminated due to unrepairable error.

    Not repairable. Restore from backup.

    p.s. Why repair in the first place? Repair should be the last resort, not the first thing tried. It's for when you have no backup and no other option.

    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

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass
  • I've had databases in Suspect mode only a couple of times, but I've never gotten them usable again. I've had to restore from the most recent full backup and then apply the transaction log backups every time. I interpret Suspect mode and meaning death.

Viewing 3 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic. Login to reply