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 two databases that are mirrored to another server using database mirroring.

The mirror server has to be down for some reason for few days.

Now, the production server is having principal databases in (PRINCIPAL/DISCONNECTED) State.

Clients can access those databases.


  • So what happens when they keep on adding data to these databases??
  • Will the data get committed or waits till the mirror comes up?
share|improve this question

migrated from Jan 3 '12 at 17:36

This question came from our site for professional and enthusiast programmers.

Your .LDF log is growing, as it cannot be truncated because the mirror is unavailable. Eventually you'll run out of space unless you either break the mirroring or bring the mirror back online.

share|improve this answer
Absolutely correct, you need to remove the mirroring and re-initialize the mirror copy when the server becomes available again. – Jason Cumberland Mar 9 '12 at 21:45

The transactions will be committed on the principle. When the mirror is up again, it will take more time to synchronize.

share|improve this answer
This is a valid option if the mirror is down for a small amount of time, but spanning days on a busy database is probably a bad idea. – Jason Cumberland Mar 9 '12 at 21:46

Your Answer


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