Skip to main content
Fixed spelling mistake in title.
Link
Mr.Brownstone
  • 13.2k
  • 4
  • 38
  • 54

Rolled back transactions during SQL Server Mirroring FiloverFailover

edited tags
Link
Hannah Vernon
  • 70.5k
  • 22
  • 177
  • 321
Source Link
Dina
  • 1.5k
  • 4
  • 27
  • 42

Rolled back transactions during SQL Server Mirroring Filover

I have two SQL Server 2014 instances setup with High Safety Mirroring for a production environment. I need to apply security patches to these servers on a regular basis which requires a reboot.

My typical process is applying patches to mirror and rebooting. Then triggering a failover to mirror and applying patches to the other server. Rebooting, then failing back.

My issue is, every failover has some uncommitted transactions rolled back and this is really not good for a production environment. I have no idea which transactions were rolled back and what kind of data loss I'm having. But I need to reboot these servers and apply patches. If I have zero data loss tolerance, what are my options?