Post reply

.net error while opening the database

  • December 6, 2011 at 2:38 am

    #247891

    While opening the database in one of my 2008 server , I am getting an error -

    Property is Datawarehouse Management is not available ........

    Please suggest

  • December 6, 2011 at 3:25 am

    #1417186

    The status of the database is in RECOVERY PENDING state .

    Pls suggest

  • December 6, 2011 at 5:52 am

    #1417277

    Please contact your DBA immediately.

    Determining the Next Step for Recovery of a File or Filegroup

    http://msdn.microsoft.com/en-us/library/ms175561.aspx

    Planning a Piecemeal Restore Sequence for a File in the Restoring, Recovery-Pending, or Offline State

    http://msdn.microsoft.com/en-us/library/ms191155.aspx

  • December 6, 2011 at 8:17 am

    #1417404

    First important question - do you have backups?

    Post the contents of the SQL error log, it'll show why the database went recovery_pending.

    To be clear, this is a severe problem and may have serious consequences (especially if you have no backups)

    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

  • December 7, 2011 at 2:34 am

    #1417875

    I restarted the sql services and it came up without fail.

    I think the prob was with the database locating the data/log files ....

  • December 7, 2011 at 2:47 am

    #1417879

    thats good that the database has come back online, but the root cause should be investigated as to why the DB went into recovery_pending and should be fixed to stop it happening again, if it should happen again.

    take a look through the SQL error logs for any indications as to what happened to the DB and take the nessesary preventative actions

  • December 7, 2011 at 7:36 am

    #1418085

    show your error.

    as you describe,maybe you can try repair your .net framework 3.5 or 4.0

  • December 7, 2011 at 7:50 am

    #1418106

    fanzhouqi (12/7/2011)

    as you describe,maybe you can try repair your .net framework 3.5 or 4.0

    It's not a .net error. It's a problem recovering the 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

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

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