Query hint for disabling table triggers for a single statement
I've got a number of applications that (mis)use triggers. Much of the logic is redundant and can be handled externally, so for particular commands, I do not need those triggers in place. I cannot disable them globally, and would love to have a query hint that would disable triggers on a targeted table for a single command without interrupting their usage for other sessions.
Martin Smith commented
In the past when I have wanted something like that I just check CONTEXT_INFO in the trigger and exit immediately if set to some value which I have defined as meaning "bypass triggers"