‘NoRecovery’ & ‘Standby’ in Logshipping?

  • What is the difference between ‘NoRecovery’ & ‘Standby’ in Logshipping?

  • NoRecovery leaves the database in a state ready to restore the next log back. There is no access to the database allowed.

    Standby will put the database in a read-only state the would allow users to query the database between restores. Doing this, you will need need to configure a means to disconnect any users that may be querying the database prior to restoring the next log backup.

  • There are two options for configuration when you place the secondary database in standby mode:

    You can choose to have database users disconnected when transaction log backups are being restored. If you choose this option, users will be disconnected from the database each time the log shipping restore job attempts to restore a transaction log to the secondary database. Disconnection will happen on the schedule you set for the restore job.

    You can choose not to disconnect users. In this case, the restore job cannot restore transaction log backups to the secondary database if there are users connected to that database. Transaction log backups will accumulate until there are no user connections to the database.

  • i am eager to ask ..

    Is that a interview question.???? :-):cool:

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

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