Post reply

Database is in suspect mode

  • October 15, 2013 at 9:15 am

    #281349

    Database is in suspect mode due to full logspace

    we already have both last night full and all transaction logs backups

    we requested extra space added to the server

    what are the good steps in bring database online after we get the extra space?

  • October 15, 2013 at 10:11 am

    #1658599

    A full log will not send a database suspect. If your database is suspect, something else is the cause.

    What does the SQL error log say?

    What's the exact value for status_desc for this database (from sys.databases)?

    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

  • October 15, 2013 at 12:37 pm

    #1658654

    you are right, full log was not the reason database became suspect but

    lite speed was blocking while database was trying to recover some transactions

    thanks

  • October 15, 2013 at 12:39 pm

    #1658658

    So is it fixed?

    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

  • October 16, 2013 at 8:28 am

    #1658938

    yes, its fixed by re-starting windows server and that stopped the litespeed that is causing the issue with the database

    thank

Viewing 5 posts - 1 through 4 (of 4 total)

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