• I too favour separate triggers for Audit and business logic/other.

    Also, at one firm, we had a third party case management system which had no auditing, an ineffective control mechanism for granular control of data changes and most of the SQL statements were ad-hoc and constructed in the compiled front-end app plus the supplier was slow/resistant to implement changes that we required. If they'd used stored procedures more widely then we'd at least have had a mechanism for implementing the changes ourselves.

    Triggers came to the rescue on numerous occasions, and although we accepted that they wouldn't have been our preferred choice, we didn't have any other option.

    It did mean that we ended up with a large number of triggers and it was far easier to have separate triggers (sometimes multiple triggers for each DML operation) to encapsulate each bit of logic that we needed to implement.