I have Merge Replication running on a central Distributor with two push subscriptions. Due to IT issues, the two 2 subscriber merge agent jobs have been disabled for some months. During this period one of the subscriber databases has been constantly updated but the other has been static. Obviously the replicated database on the distributor is also a few months out of date too.
Can I simply re-enable the subscriber merge agent jobs? I would have thought that Merge Replication should be able resume this way, albeit with a rather large merge to start with. I don't want to trigger a new snapshot as the database on the Distributor is months out of date.
If a new snapshot is required I imagine that I would have to backup up the current Subscriber (i.e. currently active) database and restore it to the Distributor before creating a new snapshot. That in turn probably require removing the subscriptions (after scripting them of course) and recreating them.
Restarting the existing agent jobs sound much simpler, if it will work.
R Campbell