Merrill Aldrich has a wonderful flow chart pertaining to database triggers. The short answer is “No.”
At one place I have worked, the primary production database had over 200 triggers, mostly to handle auditing and logging. Why couldn’t they do something like Service Broker or change tracking or some asynchronous mechanism to keep things up to date without triggers everywhere? Good question…
