I like your article but there is one place where we've found triggers invaluable: Where you have a third-party system (eg Great Plains) that you must integrate with. In that kind of a situation, business rules may call for certain data changes to be "caught" and further processing to be performed at that point. The native stored procs that come with the product may be encrypted (as are some in GP) or you may simply not want to mess with them for fear of ruining your upgrade path. In this situation, triggers make perfect sense. But I agree you wouldn't normally be relying on them.