control-behavior-of-triggers-and-constraints-in-synchronization.md

title	Control the Behavior of Triggers and Constraints During Synchronization (Replication Transact-SQL Programming) | Microsoft Docs
ms.custom
ms.date	03/06/2017
ms.prod	sql-server-2014
ms.reviewer
ms.technology	replication
ms.topic	conceptual
dev_langs	TSQL
helpviewer_keywords	identities [SQL Server replication] constraints [SQL Server], replication triggers [SQL Server], replication triggers [SQL Server replication] constraints [SQL Server replication] NOT FOR REPLICATION option NFR option
ms.assetid	7c4e0f0e-cadc-4c99-98f4-69799b9b356b
author	MashaMSFT
ms.author	mathoma
manager	craigg

Control the Behavior of Triggers and Constraints During Synchronization (Replication Transact-SQL Programming)

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

1. When creating a new trigger, specify the NOT FOR REPLICATION option of CREATE TRIGGER (Transact-SQL).

2. For an existing trigger, specify the NOT FOR REPLICATION option of ALTER TRIGGER (Transact-SQL).

To prevent constraints from being enforced during synchronization

1. When creating a new CHECK or FOREIGN KEY constraint, specify CHECK NOT FOR REPLICATION option in the constraint definition of CREATE TABLE (Transact-SQL).

See Also

Create Tables (Database Engine)