>AKAIK there's no elegent way to prevent the trigger from firing, precisely because other users can access it at the same time. The brute force approach would be to drop the trigger, perform the update, then recreate the trigger. You'd have to lock the table to prevent other users from attempting updates at the same time.
>
>This is a pretty drastic approach, as you can imagine, and best saved for after-hours processing if possible.

Would it be easier to DISABLE the trigger, rather than dropping it?