Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

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 an SQL Server 2005 mirrored database, with just the primary and secondary servers, no witness. Tonight the primary has gone down and will not be back on-line for some time yet. The secondary server is still running, but is "Mirrored, Disconnected / In Recovery". How can I get the database back up and running? My applications are all using a string that specifies the primary and secondary servers.

share|improve this question
up vote 4 down vote accepted

I believe if you are not using a witness you can still enable the mirrored instance by using Forced Service. This method should pass the services on to your mirror but there is a risk of data loss. This technet article should be able to start telling you the involved processes as well as the risks involved.

The T-SQL to force the mirror to take over is:


With database_name being the name of the mirrored database. This must be run on the mirrored server.

Make sure you read the article before doing this so you know of any potential risks going in.

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.