Tuesday, December 4, 2007

SQL:NOT FOR REPLICATION



Create a transaction publication:

Modify the articles' properties:Copy foreign key constraints, Copy check constraints, and Copy user triggers are changed to TRUE.
If Foreign Key Constraint, Check Constraint, and User Triggers are not copied to Subscribers, they are definitely not enforced. After they are copied to the Subscribers, NOT FOR REPLICATION option will make the differences.


If you encrypt your triggers, they are not copied to the subscribers.

If a row is inserted by a user at the Publisher and that insert satisfies a check constraint on the table, database engine will not enforce the same constraint when the row is inserted by a replication agent at the Subscriber.