Home Forums SQL Server 7,2000 Data Corruption DB corrupted with event 17052 and Error: 823, Severity: 24, State: 2 RE: DB corrupted with event 17052 and Error: 823, Severity: 24, State: 2

  • halifaxdal (9/13/2011)


    Ninja's_RGR'us (9/13/2011)


    halifaxdal (9/13/2011)


    GilaMonster (9/13/2011)


    Run SP_configure and set allow updates to 1. Update sysdatabases for that database and set the status to 32767.

    Then see if you can access the DB and run checkdb. Not repair, just with the no_infomsgs and all_errormsgs options.

    can you elaborate? i thought before SP_configure i have to be in that db, and it won't let me in that db. meaning the following won't work? or I just need to use in master?

    use sels

    go

    sp_configure 'Allow updates',1

    go

    You can run that anywhere, it's a server-wide setting.

    What do you mean 'won't let you'? It's going to require sysadmin permissions, as will just about everything else.

    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