Home Forums SQL Server 2005 Data Corruption Database in "suspect" mode (SQL Server Management Studio 2005) RE: Database in "suspect" mode (SQL Server Management Studio 2005)

  • A critically important database with no backups that's suspect. Usually I'd say URLT, but not applicable in this case unfortunately.

    What you did could not cause the suspect status. Recovery pending maybe, but not suspect. Suspect means that the database engine encountered some form of corruption while doing crash recovery.

    What is the current situation?

    If there's still a suspect DB...

    Query sys.databases and post exactly what the state_desc for the database is

    Open the SQL error log and find any and all messages relating to this database.

    The error on checkDB is, as ALZDBA said, due to the quotes. There's a ` where there should be '

    That said, you can't run checkDB on a suspect database. Hence the request for the database state and error log.

    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