November 21, 2002 at 12:08 am
I have to replicated data among three Sqlserver2000 on different sites. These servers need to be highly autonomous. One of the servers has a fixed IP and others will be just connected to Internet. Other 2 servers will be able to connect to it through IP.
I tried Merge Replication on different machines of a same network, but have not tried it on Internet. My first question is
Q1: Should I need some special consideration for replication on internet?
But this is not the main concern right now. I need to know
Q2: How can I resolve conflicts in merge replication?
The scenario that i faced was. I have surrogate keys in most of the tables. The database is the same on all sites. It normally happens that same keys are generated on all the sites while insertion (due to autonomy on all sites). Then during replication (push subscription on a server) the publishers record will be replicated on all the sites and the records (with same ID) on subscribers will be deleted.
Whereas what i want is to get the three records after merge replication in all the servers. The repliation has introduced its row_guid coloumn also but it is not used in the scenario mentioned above. So how can i do it manually that <b>"During replication the same IDs with different row_guid should be merger not updated".</b>
I have seen some discussion on autogenerated triggers in case of merger replication but i dould'nt find any triggers created in my test setup.
Where can i find detail help on this also?
Any help in this regards will be appreciated.
Regards
Mustafa
November 21, 2002 at 10:19 am
In response to your second question, you need to use different identity ranges on each server, so that there will never be "duplicate" IDs. Search for "Managing Identity Values" in BOL.
Jay
Jay Madren
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply