Post reply

Extent (1:205976) in database ID 6 is marked allocated in the GAM, but no SGAM or IAM has allocated it.

  • September 14, 2010 at 9:44 am

    #1220784

    Do you have any backups dating back to before 19th Aug, and is losing a month's data acceptable (note that I don't know how much you'll lose doing a repair, I have asked someone to step in here)

    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

  • September 14, 2010 at 9:50 am

    #1220791

    Yes but im still waiting for my Manager to approve.

  • September 14, 2010 at 10:08 am

    #1220808

    What I'd suggest first is that you take a copy of this database, put it onto a dev/test server and then run CheckDB with the repair_allow_data_loss option. See what repairs are made and how much data is lost by that operation. Then decide between the repair and the restore from a month ago.

    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

  • September 15, 2010 at 1:06 am

    #1221140

    I think that's a good idea, i will do that and show you the results.

  • November 23, 2011 at 11:11 pm

    #1412556

    hi - any news on this? We are having the exact same problem.

  • November 23, 2011 at 11:26 pm

    #1412559

    Hi,

    I had to restore an old backup in order to overcome this.

    So if you have the same situation, that's pretty it. You need to restore an old backup and run checkdb.

Viewing 6 posts - 16 through 20 (of 20 total)

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