When replication are created do they create triggers to replicate data?if yes how can i run my triggers before replication triggers.
View Complete Post
Currently running merge replication on SQL Server 2008 10.0.1600 and having issues with adding and modifying triggers on published articles. I've searched through the MSDN site and googled it but have not found any definitive information on correct
We have a replicated table that had 1 trigger on it when it was added to the publication. That trigger was replicated. We have since added a 2nd trigger to the table and it is not being replicated to our other server. I've checked the Article
Properties and Copy User Triggers is set to TRUE. The only difference is the new trigger has NOT FOR REPLICATION in it, but I thought that would only keep it from being executed if a row is effected by the MERGE process.
We have rerun the snapshot and are syncing continuosly and the trigger does not replicate. Do I have to drop the tablefrom the publication and then re-add it? Am I missing something?
When replication created do they create triggers to replicate the data? if yes can i make my triggers run before replication triggers.
I have a few triggers created on the subscriber that fire whenever a certain table gets updated with a row. The Replication is transactional and the has a latency about 14 mins.
1. What problems can triggers cause and what all do i need to be aware off?
I had created triggers earlier on the subscription and they failed the entire replication as it on error it tried to rollback transaction. Please help. Thanks
Is it possible to force SQL Server to add NOR FOR REPLICATION attribute to all triggers while they are being transfered to subsriber? Or manually I should alter them one by one?
Many thanks in advance,
What to do when you need to disable triggers and constraints to perform data synchronization and other tasks with an offline database.
MSDN Magazine April 2007
MSDN Magazine January 2004
MSDN Magazine December 2003
MSDN Magazine September 2003