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?
Sql-server – SQL Server full safety mirror commit overhead less then Time to send
mirroringperformancesql serversql-server-2008
Related Question
- Sql-server – SQL Server Mirror failover on failing storage
- SQL Server 2008 R2 Readable Mirror – Setup and Configuration
- SQL Server – How to Safely Delete Transaction Log in SQL Mirroring Scenario
- SQL Server 2012 – Login Issues on Mirror Server
- Sql-server – SQL Server 2012 Transaction Log needed to create database mirror
- Sql-server – Database Mirroring – Will forcing the service only lose non-committed data
Best Answer
Database Mirroring Monitor (Status Page):
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).