I had some trouble with a transactional replication and I had the bad idea ( so far it seems ) of reinitializing the synchronisation.
The snapshot agent ran, and now it wants to apply the snapshot data on the subscriber.
The problem is with my setup...
I have a workstation A and workstation B that use merge replication. There is also a transactional replication between workstation A and server C.
Now the distribution agent wants to drop my table and repopulate it, but it cannot be done because of the merge replication already going on.. and it would screw the setup as we need to setup merge then transactional replication in that order.
I have backups of all the tables on each server/workstation if that can be done this way ( by restoring the distribution database for example ).
So... is there any way to cancel the application of the new snapshot data or to trick it to think it's been done?
Last time this happened to me I simply went to the workstation location and redid all the configuration from the beginning since it's not very long and there is not much data. However, this time, this is a remote location and we cannot do it remotely for internal office/political reasons.
Thanks for the advices!