My supervisor is hesitant to use a trigger in a process because if there is a network interruption at just the right time, the process would not complete. Does SQL Server include the trigger in the calling procedure's transaction? If not, what is the best way to implement this?
There are quite a few situations when triggers do not fire, such as:
· A table is dropped.
· A table is truncated.
· Settings for nested and/or recursive triggers prevent a trigger from firing.
So, in SQL Server a trigger is NOT guaranteed to execute. Sometimes it can be bypassed.
Also a trigger may be just incorrect. Either way, you may end up with orphans in your database.
If you post what you are trying to accomplish with your trigger, maybe we can help you implement it with constraints.
Yes. Triggers occur as an implicit nested transaction within the scope of the caller's transaction. The trigger till commit or roll back as part of this transaction.