I use a lot of triggers in my applications and sometimes I would like to suppress the trigger for certain processes. Such as the audit trigger when updating a large table. Because I usually perform these procedures at night when no one else is using the database, I currently drop the trigger when I start the routine and then add it back at the end of the procedure. It works fine except that the trigger is then not active for other users that may log onto the system unexpectedly.
I think that I may program a switch into the procedure to bypass the code in the trigger procedure but I thought that I would ask how other developers handle this issue. I tried using the ABORT TRIGGER in the procedure but it did not suppress the trigger. Any input will be appreciated. John
