We have a situation almost exactly like that in the MS documentation
vis a vis peer-to-peer replication. We have three servers and three
user groups, one each in Chicago, New York, and Bermuda. Because of our
business practices, we are fairly confident that only one group will be
updating a given record at any one time but the users will be updating
their own local database servers and those updates must appear on all
three servers. Reading through the documentation, MS seems to recommend
peer-to-peer merge replication. Unfortunately, the documenation then
goes off and gives an example only of transaction replication without
updating subscriptions. Well, OK I sez, I'll just adpat what the docs
say but select merge replication. Doesn't work that way. Using SQL
studio, I have never been able to get to a peer-to-peer topology option
using anything but transaction replicas without updating subscriptions.
Using T-SQL, it looks like I can brute force peer to peer replication
with updating subscriptions but the sp_addmergedpublication function
does not have any options for peer-to-peer topology.
So, what gives? How do I set up peer-to-peer merge replication? Any
help would be greatly appreciated!
Thanks.
Randy
