We are having a symmetry issue between rep over a LAN and over the WAN. I want to know the roll of the MSDTC and possible two-phase commits (2PC) that may be occurring with certain subscription types. It didn't seem the replication stream scales well over the WAN and 2PC are not the thing to do over longer distances due to the excessive amount of handshaking needed in 2PCs (reflectivity issues).
If 2PCs and the MSDTC are used, are certain setups or types of replication in SQL 2005 available that would be more efficient over a long distance WAN? Can 2PCs be avoided?
The setup that was built with the issues is not a typically built replication topology (by my book). By my own rule, I never place the distributor on the publisher, ever. Apparently, when setup this way, I didn't have any issue replicating over a similar WAN. Does the distributor work differently when running on a dedicated server?
What's the best replication topology when attempting to replicate over a long distance WAN?
Thanks.
Transactional replication works well over a wan. If you are replicating DML which modifies large numbers of rows consider replicating the execution of stored procedures.
Immediate updating does use MSDTC when transactions originate on the subscriber. Other replication types do not.
No comments:
Post a Comment