How to: Control the Behavior of Triggers and Constraints During Synchronization (Replication Transact-SQL Programming)
Aktualisiert: 14. April 2006
During synchronization, replication agents execute INSERT (Transact-SQL), UPDATE (Transact-SQL), and DELETE (Transact-SQL) statements on replicated tables, which can cause data manipulation language (DML) triggers on these tables to be executed. There are cases when you may need to prevent these triggers from firing or constraints from being enforced during synchronization. This behavior depends on how the trigger or constraint is created.
To prevent triggers from executing during synchronization
When creating a new trigger, specify the NOT FOR REPLICATION option of CREATE TRIGGER (Transact-SQL).
For an existing trigger, specify the NOT FOR REPLICATION option of ALTER TRIGGER (Transact-SQL).
To prevent constraints from being enforced during synchronization
- When creating a new CHECK or FOREIGN KEY constraint, specify CHECK NOT FOR REPLICATION option in the constraint definition of CREATE TABLE (Transact-SQL).
Siehe auch
Andere Ressourcen
Erstellen und Ändern von Tabellen
Steuern von Einschränkungen, Identitäten und Triggern mithilfe von NOT FOR REPLICATION