September 28, 2011 at 3:11 pm
I have one publising Databae with one publication and two subscribers.
On occasion I would like to re-initialize the subscriber but I do not want them loading at the same time. I would always like to have at least one replicated DB available to my application. Eventually I would like to scale out to 3 or 4 replicated DBs.
How can I gernerate one Snapshot and then schedule the replications to re-initialize from that snapshot at different times?
If I mark both replications to reinitialize and then generate a snapshot, when the snapshot completes both replications will begin to load at the same time which makes both repicated DBs unavailable to my end application(s).
If I mark one replication to reinitialize and then generate a snapshot, when the snapshot completes the one reinitializes as expected. If I then mark the second one to reinitialize the option to use an existing snapshot is disabled. How can I force the replication to reinitialize from a previously generated snapshot?
Thank You in advance for your help
October 10, 2011 at 10:32 am
Stop the distribution agent for one of the subscribers. In a push topology you will find it on the distributor, in a pull one you'll find it on the subscriber. It will be running as a sql agent job (in 99% of cases).
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply