Yes, it is doable. The replication engine is issuing transaction, just as any other application would. So, yes,...
it will cause triggers to fire. If you wish to suppress triggers from firing when the replication engine is applying transaction, then you would add the "not for replication" option to the trigger.
For More Information
- Dozens more answers to tough SQL Server questions from Michael Hotek are available here.
- The Best Microsoft SQL Server Web Links: tips, tutorials, scripts, and more.
- The Best SQL Web Links
- Have a SQL Server tip to offer your fellow DBAs and developers? The best tips submitted will receive a cool prize. Submit your tip today!
- Ask your technical SQL Server questions -- or help out your peers by answering them -- in our live discussion forums.
- Ask the Experts yourself: Our SQL, database design, Oracle, SQL Server, DB2, metadata, object-oriented and data warehousing gurus are waiting to answer your toughest questions.
Dig Deeper on SQL Server Replication
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.