Restoring replication triggers
-
I have found myself in the position of having to fix some errors created by a recently "departed" DBA who managed our merge replication. Apparently, a replicated table on a subscribers database was missing triggers. The other DBA decided to fix by copying the triggers from another replicated database. Of course, this did not work because the views refered to in the triggers did not exist due to the uniqueness of names via guids. In order to get the site backup and working, I had to drop the replication ins_, del_ and upd_ triggers.
So now, how do I who is not well versed in replication (but currently learning by fire) restore those triggers?
Please HELP!!
Gordon Pollokoff
"Wile E. is my reality, Bugs Bunny is my goal" - Chuck Jones
-
Well, I am not sure if there's a good way to handle it by manually recreating the triggers. One thing I can think of is restoring a pre-drop backup of the database to another location and scripting out the triggers from there. I'm not sure what the consequences of doing this might be.
The way I'd end up handling it would be to drop the subscriptions / publisher from the replication scheme and recreating the publication. This should reupdate all the tables and put the replication schema information back in place. I know it sounds drastic, but it's probably the most thorough way of taking care of this.
Beyond that, I wish you luck in finding a way to handle this.
-
Thanks. I figured that would be the way but I was hoping there would be a faster, simpler way. Apparently, so did my predecessor
Gordon Pollokoff
"Wile E. is my reality, Bugs Bunny is my goal" - Chuck Jones
-
you're welcome. yeah, sometimes shortcuts just aren't worth it, especially in a production environment.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply