We started several merge replication abroad 1 year ago, and everything is going well so far. My problem is that we now have so much data in our system that any accident on one of the subscriber servers will be a disaster: re-initializing the subscription in the standard way will take several days (our connections are certainly slow, but already very expensive)! Among the ideas I followed were the following:
- make a copy of the original database, freeze it, send files on the plane to the subscriber, and initiate replication without a snapshot: this is what was done traditionally with older versions of SQL, but it sounds a little messy for me: I would put my publisher data into read-only mode and stop everything until the operation is completed.
- take a snapshot of the data, send the snapshot files abroad, install them on the subscriber and specify the new location of the snapshot as an alternative place in the replication properties. This one sounds fair to me (there is no need to suspend current replications, do not freeze data), but Microsoft does not help with this ... help.
I am sure that some of you have already experienced this situation. What was your choice?
EDIT: of course, you can say, “Why don't you just try your ideas,” but it will take several hours (several instances of sql servers, virtual machines and all this ...), and I thought the guy who did it it will take only 2 minutes to explain his idea. And I would be the happiest person if someone agrees to lose 2 minutes of their time to save me from hard work ...
source
share