Export (0) Print
Expand All


Topic Status: Some information in this topic is preview and subject to change in future releases. Preview information describes new features or changes to existing features in Microsoft SQL Server 2016 Community Technology Preview 2 (CTP2).

Product Name

SQL Server

Event ID


Event Source




Symbolic Name


Message Text

The alert for 'mirror commit overhead' has been raised. The current value of '%d' surpasses the threshold '%d'.

This database mirroring event is issued on the principal server instance to indicate that the aggregate commit wait time reached or exceeded a user-specified threshold value because of database mirroring. The wait time is the product of the number of transactions and the time of each. For example, the following cases both produce 1000 milliseconds of wait time: 1000 transactions * 1 millisecond, and 1 transaction * 1000 milliseconds. An increased commit wait time can be caused by a surge in the transaction count, delays in sending the log, or delays in flushing the log on the mirror server instance.

The amount of mirror commit overhead is a performance metric that can help you evaluate the current performance impact of synchronous operation. This metric is relevant only in high-safety mode. Because high-safety mode is synchronous, the principal server instance waits to commit the transaction after it sends a log record to the mirror server instance until it receives confirmation that the mirror server instance has written the log record to disk. The log record remains on disk on the mirror server instance while it waits to be restored to the mirror database.

Check the loads on the principal and mirror server instances and their network connection for the cause.

Was this page helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

© 2015 Microsoft