db suspect mode

  • Hi All

    My Database as gone to suspect mode.how should i get back it.

    My db size is 8gb.plz help me out its very urgent

  • How to recover depends completely on what's actually wrong. Check the SQL error log, there should be error messages indiating why the database is suspect. Check those messages, post them here.

    Do you have a backup of this database?

    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
  • where can i check my error logs.plz help iam new to sql server

  • In management studio open Object Explorer. Management - SQL Server Logs.

    If there's a senior DBA there get him involved. Suspect database are serious issues. If not, consider calling MS's customer support. They'll charge, but they will walk you through the steps to get the DB back, if possible.

    You haven't answered my question. Do you have a backup of this database?

    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
  • Hey thanks for helping me for error log navigation.ya we have a backup of this data base.

    I am getting this type of error

    could not opne the .mdf fiel locaiton.

    could not open the device with event id:17055 type :error category:2 db in suspect modein sql server 2000

    event id 17055

    type :error"category:2

  • Please post the exact messages from the SQL 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
  • I'd suggest you cut and paste a portion of the log that applies. I realize that you might be frustrated, or in a hurry, but your typing has a bunch of errors, and we might not get the correct information or post the appropriate advice if we don't get the exact data.

    Be sure that all your disk drives are available when SQL starts. Often if one is slow or not responding, then SQL marks the database as suspect.

Viewing 7 posts - 1 through 7 (of 7 total)

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