Question 29

Answer E is correct. Triggers usually perform their work when changes occur within the data. In a replication scenario, you usually don't want those procedures to be performed in both the source and destination locations. To prevent that from occurring, you can set the trigger as NOT FOR REPLICATION so that it will not fire in the destination. This option can also be applied to identity columns and constraints. Disabling or dropping the triggers is likely to remove required functionality at the source.

For more information, see the following sources:

• Chapter 3, "Implementing Database Objects"

• SQL Server 2005 Books Online: "SQL Server Replication, Configuring and Maintaining Replication, Implementing Replication, Implementation Considerations for Replication, Considerations for All Types of Replication, Controlling Constraints, Identities, and Triggers with NOT FOR REPLICATION"

• "ALTER TRIGGER," http://msdn.microsoft.com/library/default.asp?url=/library/en-us/tsqlref/ts_aa-az_9036.asp