August 20, 2015 at 9:50 am
Hello
I'm fairly new to replication and have what I hope is a relatively quick question.
We use transactional replication and the publication database is worked on by an external company every few months. This quarter the replication was removed by them, and they claim that it stopped some of their scripts from running so they had to remove it. (We didn't know an 'upgrade' was taking place)
I've tried to find out what errors they received/what they were trying to do so that I can gain a better understanding and also have a plan of action for the future (I'll be honest, I'm not a DBA) but my questions don't seem to be going anywhere.
I gather that certain actions for example, dropping/recreating published objects cannot be done. However from what we know, the company doesn't do anything like this. Can replication prevent anything else from happening on the published database?
If so, would it be enough in future to simply stop synchronising and the replication agents, or does it really need to be removed every time?
Thankyou in advance!
Viewing 0 posts
You must be logged in to reply to this topic. Login to reply