January 5, 2007 at 12:44 am
Hi,
We have been managing SQL Server application for a client, where data replication (Merge replication) has been setup from a remote location (By default India !) to a location situated in West coast of USA.
Due to recent earthquake in Taiwan our link (IPLC) is down since 12/27 and our data link is yet to restored. We have pending data for replication for data captured on 12/27.
Since we have Internet connectivity, we manually ported the data (insert/update @ from subscriber to Publisher) pending for sync and subsequently asked our Indian users to connect to the server in West coast(via VPN).
We have about 50 databases and all our databases are merge replicated.
Once the IPLC link is restored, there will be conflicts (since we have manually inserted the data from the subscriber end to the publisher) which can be classified
a. Primary key conflicts (since we have manually inserted subscriber data at the publisher)
b. Update conflict (normal)
c. system deletes (any other issues requiring review)
Let me know whether any other way we could have achieved this
I shall share with the forum of my expereince once the data link is restored.
Does any body had a similar experience in the past. Would like to hear/learn from this.
Rangark
January 6, 2007 at 2:35 am
Use the "-SkipErrors" parameter in Distribution Agent cautiously
http://support.microsoft.com/kb/327817
MohammedU
Microsoft SQL Server MVP
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply