February 17, 2003 at 10:40 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.
--------------------------------------------------------------------------------
February 20, 2003 at 8:00 am
This was removed by the editor as SPAM
February 20, 2003 at 9:12 am
How about modifying the trigger to write to a log table, or just put a raiserror in the trigger, or even just adding a rollback?
Andy
March 7, 2003 at 12:10 pm
more to the point on logs... I'm pretty keen on xp_logevent, as it doesn't cause replication to blow up (like raiserror) and you don't have to create a table for logging purposes.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply