The downside of using some place like context_info is that it is unique (per session). Are we sure that our trigger is the only one that uses it ? Are we sure that context_info is used (by other developers in our organization) only for bypassing triggers ? If there are other triggers that use it, should all triggers be bypassed (would we never like to bypass only some triggers) ? If answer to all these questions is yes, then we can use context_info (and it seems better than other methods, because sysprocesses is always in memory); if not, then we should use one (or more) table(s) for configuring trigger bypassing.

Another interesting (not necesarily bad) thing: although context_info is stored in a table, it ignores transactions (it is not affected by rollback-s).

Razvan