February 11, 2003 at 10:33 pm
I would like to have an update trigger fire on the subscriber after transactional replication has updated specific tables. I have tried to implement this and it seems that replication updates at the subscriber don't fire triggers. Does anyone know why, and is there a work around?
February 12, 2003 at 6:36 am
Are you using replication stored procedures, those like sp_MSupd_TableName? We have also transactional replication and we have trigger on both the publisher and subscribers.
February 12, 2003 at 12:23 pm
Make sure the triggers were not somehow marked with the NOT FOR REPLICATION clause.
February 13, 2003 at 5:47 pm
Racosta...
Thankyou for your reply:
quote:
Are you using replication stored procedures, those like sp_MSupd_TableName? We have also transactional replication and we have trigger on both the publisher and subscribers.
Yes I am using transactional replication, and these are the types of triggers that are generated at the subscriber.
RossL
February 13, 2003 at 5:52 pm
Brian,
I have checked my triggers, and they are not using the "NOT FOR REPLICATION" parameter.
I am still having trouble, I know the replication update is working, but I cannot find out whether my subscriber trigger is firing. I have checked the SQL Logs and can find nothing that relates. Is there any way I can find out what is happening when the subscriber update trigger fires?
RossL
quote:
Make sure the triggers were not somehow marked with the NOT FOR REPLICATION clause.
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply