October 23, 2013 at 4:08 pm
I have a problem with initiating merge replication over slow VPN. It is fairly big - 11GB. Every time i try to initiate DB, i get some sort of error (losing connection or not enough memory for example) and whole process needs to be restarted.
I have other smaller DBs that are replicating fine.
Is there any way of helping replication for example by copying snapshot over FTP?
Thanks,
Pete
October 28, 2013 at 10:50 am
Pete, you are creating a publication MERGE and applying a snapshot at the subscriber, right?? The problem can be solved as follows:
1. Create empty tables on the subscriber;
2. Make a DTS publisher to the subscriber tables;
3. And finally create the signature without IPL, so it will only create a snapshot with the triggers and apply them to the subscriber.
I had problems like this and decided that way.
Hugs.
January 8, 2014 at 6:14 pm
Another option is if you can use pull replication (the subscriber has to be full SQL, or MSDE 2000, not SQL express).
Basically you create the snapshot, zip the files, and copy them over the wan. Once you have gotten the files in place, create the subscription, and set the snapshot location to a local directory on the subscriber. Unfortunately with SQL 2005 and up you can't do this when you are setting up replication, and have to quickly do it after you create the subscription, and open the subscriber properties, and change the snapshot location to the alternate location. We do this over slow links
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply