hi, experts,

if my database (2014) enables replication , maybe transactional replication.

further, trigger (insert, update, delete) is enabled on some database tables.

but this setup, will it hit performance issue on sql server?

thank you very

The UPDATE would already be affecting the performance of the INSERT if it affects an index, even without the trigger in most cases.

Hi delaynomore,

We should avoid creating triggers on tables that contain subscribed data. Business logic in user-defined triggers at the subscriber can significantly add to overhead and slow replication performance, including snapshot replication, transactional replication, and merge replication configurations.

In addition, with regards to triggers at the publisher, there is a "not for replication" configuration that you need to consider applying to control their behavior.

Reference:
Enhance General Replication Performance
Controlling Constraints, Identities, and Triggers with NOT FOR REPLICATION


Thanks,
Lydia Zhang

Publisher side triggers will not cause performance problem with replication per se. Subscriber side will unless you use the not for replication switch.

By default triggers on published tables will not be created on the subscriber side.

hi, Hilary, I did not see anything about subscriber and Publisher. are these 2 terms from replication knowledge area?

Thank you very much!