Some sessions are suspended after Mirroring Safety is set back to Full - by Jean-Nicolas BERGER

Status : 

  Won't Fix<br /><br />
		Due to several factors the product team decided to focus its efforts on other items.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 775741 Comments
Status Closed Workarounds
Type Bug Repros 1
Opened 1/3/2013 5:10:48 PM
Access Restriction Public


In a Database Mirroring configuration, if the operating mode is set to high performance asynchronous and then set back to high safety with automatic failover, then some data modifications made during the high performance phase are blocked by a DBMIRROR_DBM_EVENT wait.
Sign in to post a comment.
Posted by Jean-Yves [MSFT] on 1/14/2013 at 1:24 PM
Hi Jean-Nicolas,
thanks for taking the time to share your feedback, this is really important to us.
We will investigate the issue and get back to you.

Best regards
Jean-Yves Devant 
Program Manager Servicing and Lifecycle Experience of High Availability Technologies in SQL Server
Posted by Jean-Nicolas BERGER on 1/10/2013 at 12:27 PM
Thank you Jonathan, your workaround is great because the availability of the primary database can be nearly maintained if the restart of the secondary instance is done quickly enough.
Posted by Jonathan MacCollum on 1/6/2013 at 1:24 PM
I encountered this issue today in my lab (running SQL Server 2008 R2 - CU6)... I submitted a possible workaround.
Posted by Jean-Nicolas BERGER on 1/3/2013 at 5:11 PM
Note : the problem occurs on SQL Server 2012 SP1, and already occured on SQL Server 2008 R2 SP2.