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

How is it possible that the time to send value is greater then the mirror commit overhead? The mirror operates under full safety so this means that the commit is only done @ principal when the commit is successful @ mirror. When the time to send is 2 seconds, this should mean that that overhead is at least 2 seconds. Or am I missing something?

enter image description here

share|improve this question
up vote 2 down vote accepted

Database Mirroring Monitor (Status Page):

Time to send log (estimated)
Approximate amount of time the principal server instance requires to send the log that is currently in the send queue to the mirror server instance (the send rate). Because the rate of incoming transactions can vary significantly, the time to send log is an estimate. However, the send rate can be useful for roughly estimating the time required for a manual failover.

The time to send measures the time to send all the pending log. It only applies if there is a pending log (eg. the principal has run exposed and mirror is in 'synchronizing' state). Notice that in this state the principal does not wait for commits to be acknowledged by mirror, hence the commit overhead is significantly lower (1-5 ms) than when running in 'synchronized' state (20-40-80ms).

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.