December 17, 2010 at 5:10 am
Hi All,
I am using Transactional replication with updatable subscriptions with queued updating to replicate between geographically separated servers over a WAN. Replication from publisher to subscriber replication appears to cope with outages to the WAN much better than replication from subscriber to publisher (Queue reader Agent). At the moment I am setting up replication using the wizard in SSMS.
Is there anything I can configure to make replication from subscriber to publisher more robust? Also, what is the best way to monitor replication from subscriber to publisher (trace tokens only appear to work from publisher to subscriber)
If the robustness cannot be improved I’ll have to consider other replication methods: Is Merge replication or Peer-to-Peer transactional replication likely to be more reliable? It will be difficult to switch to Peer-to Peer replication because I am currently using SQL server standard edition and I understand that Peer-to-Peer transactional replication is only in the Enterprise Edition.
Any help would be appreciated!
December 30, 2010 at 9:38 am
Have you configured the subscribers to use queued updates? This can be done at the replication\subscriptions node on the subscriber.
January 4, 2011 at 4:18 am
Thanks for the reply!
Yes we are configuring the subscribers to use queued updates.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply