January 25, 2010 at 11:42 am
If i get a network issue between my mirror and primary, and am using synchronous mirroring, is this a sure way of getting long running transactions.
just had a case where the primary could not hit the mirror, and then the server's memory filled up and the sql service needed a reboot before we could access the server. couldnt even access the DAC. logs dont show anything except they do mention the mirroring issue, and a long running tran, and im wondering if the two are linked.
January 25, 2010 at 12:16 pm
winston Smith (1/25/2010)
If i get a network issue between my mirror and primary, and am using synchronous mirroring, is this a sure way of getting long running transactions.
Maybe. Depends whether it's slow or broken network.
Slow, yes, you will have long-running transactions because the write to the log must happen both sides before the commit is considered done.
If the network's down, the mirroring will switch to 'disconnected' and the principal's tran log will fill up with transactions that need to be pushed to the mirror.
Don't ever try running synchronous mirroring across a slow WAN. It's asking for loads of trouble. (been there, done that)
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
January 25, 2010 at 12:35 pm
dont think it was slow. getting a load of errors saying principal db canot contact mirror db on mirror server. more like an outage than sluggish network. il go through the logs in a bit more detail and see if i can see anything more. thanks
January 25, 2010 at 12:44 pm
The principal should detect that the mirror's not accessible and go into the disconnected state. Should.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply