primary database coruppeted,it is in the suspected mode want to retrive

  • Messages from the SQL error log please.

    Exact errors you got when querying the DB please.

    I'm not able (or willing) to help without both. I don't want paraphrased descriptions. Exact messages.

    As I mentioned before, if this is critical, call Microsoft's customer support. $250 is nothing compared to what a prod database down for 2 days can cost a company.

    p.s. SELECT @@version?

    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
  • GT-897544 (2/23/2010)


    What is the status column value when you query select * from sysdatabases.

    since this is in the 2005 forums (and hence should be a 2005 database) SELECt state_desc from sys.databases is a far better option than sysdatabases, unless you like decoding bitflagged values.

    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
  • Hi All , now proble was resolved , it came into the normal stage .

    the below procedure is what i run to get from the suspected mode to normal mode

    EXEC sp_resetstatus 'DBname'

    ALTER DATABASE DBname SET EMERGENCY

    DBCC checkdb('DBname')

    ALTER DATABASE DBname SET SINGLE_USER WITH ROLLBACK IMMEDIATE

    DBCC CheckDB ('DBname', REPAIR_ALLOW_DATA_LOSS)

    ALTER DATABASE DBname SET MULTI_USER.

    Thanks for all the help.

    regards

    sat

  • Please be aware that by using the ALLOW_DATA_LOSS repair option you may have done just that, lost data. Please start a scheduled backup plan immediately so that if this occurs again you will have backups that you can use to recover instead of potentially lossing data.

  • personally I would then run another checkdb to make sure the DB was now clean.

    ---------------------------------------------------------------------

  • just now i run the check db.

  • And?

  • Lynn Pettis (2/24/2010)


    Please be aware that by using the ALLOW_DATA_LOSS repair option you may have done just that, lost data.

    However it is the only repair level allowed when the DB is in emergency mode.

    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

Viewing 8 posts - 16 through 22 (of 22 total)

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