(Restoring...) question

  • Hi everyone.

    Could anyone help with this one.

    A database has incorrectly been restored with (RESTORE WITH NORECOVERY) configured, therefore database is in (restoring) state post completion of restore.

    is the only way to bring the database back on line is to do another restore with correct recovery option configured ?

    Backup is coming from Veritas backup.

    cheers for any tips or advice.

  • Run

    RESTORE DATABASE <database name> WITH RECOVERY

    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
  • Thank you 🙂

  • MickyD (1/5/2013)


    is the only way to bring the database back on line is to do another restore with correct recovery option configured ?

    The answer is "yes and no". The command to run is the one that Gail posted with the understanding that if the database has already been restored and is just waiting for the final recovery step, then it won't actually go through another full restore. All it will do is go through the final recovery step (which usually takes less than a second on most databases) to bring the database on line.

    --Jeff Moden


    RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
    First step towards the paradigm shift of writing Set Based code:
    ________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

    Change is inevitable... Change for the better is not.


    Helpful Links:
    How to post code problems
    How to Post Performance Problems
    Create a Tally Function (fnTally)

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

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