>That is an important detail I overlooked at first. It turned out, DBA Admins would run update statements to correct/change data based on specs and those changes were not in their audit reports. So it raised questions why some values existed without corresponding audit. So Triggers would have solved this problem for sure.
>Disadvantage is that if your application supports different backends, you certainly have more work at hand.

Yup, I've had the exact same thing happen before, and that's largely why I advocate them. I've had a devil of a time trying to figure out why key configuration settings changes, and it took some major inquisitions with a DBA to find out they changed them manually.

Yes, having to support multiple back ends is a challenge. Oracle has some trigger functionality that SQL Server does not. I agree.