Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have 2 servers on SQL Server 2005 SP4. When the secondary server catches up with the log files it is switches into standby mode, but after a while it seems to be 'stuck' in restoring.

There were some open connections & queries on the database, but these have now been closed. The copy and restore jobs are running fine, but its not being switched into standby. Can't see any transactions in the dmvs.

Can I attempt to manually restore the database with STANDBY option to switch it into standby? or will this break the log shipping (need to be careful as snapshot 300GB from a live website)

or is there anything else I need to check for task, etc blocking the switch to Standby..


share|improve this question
up vote 3 down vote accepted

Turns out the log shipping configuration has reverted to NORECOVERY instead of STANDBY.

I think the is that there must have been an open session on the database, SSMS or alike and after a set period the log shipping is configured to revert back to NORECOVERY. The original configuration was did not have the 'disconnect users currently connected' option enabled.

To resolve the issue I simply went back into the original database and selected ship transaction logs and then selected the radio button for STANDBY instead of NORECOVERY

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.