I noticed my triggers weren't being fired after a subscriber was reinitialised. Is there a configuration to allow this functionality.

Currently my setting for 'Action if name is in use' is 'Delete data' so I know my triggers aren't being deleted after the table is reinitialised.

I have already confirmed that the trigger works by manualling inserting a row in my publisher database.


1 Answer 1


re-creating the triggers after I run the snap does the trick for me.

The way I do it and it has always been worked is the following:

Before I run the snapshot and reinitialize the subscriptions, I go to the subscription databases and script out all the permissions, triggers, synonyms, and in some cases the indexes (when indexes in the subscription are different than the indexes in the publisher).

when running and applying the snapshot it basically will re-create all the tables (that are part of the publication)

so if you do a select * from sys.tables you will see the create date of those tables.

Basically right after you run the snap, you then need to apply all those scripts you previously generated as I mentioned before (permissions, triggers, synonyms, indexes). there is even a place you can set up the script to be run immediately after you run the snap so it does it automatically for you.

Just make sure you have all the permissions set to read a file that is saved somewhere.

enter image description here

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.