Hugo Kornelis - Sunday, May 21, 2017 3:03 AM
Another upvote. I like the idea in the item, allthough I'd like just implementing BEFORE triggers even better.
However, I do not share your dislike for INSTEAD OF triggers. They are a great tool for some specific purposes. I have used them to expose views as if they were the base tables, hiding the actual base tables, and allowing full updatability even when SQL Server itself would consider the view non-updatable or misunderstand how to change the base tables to correspond to the actual change,
[/quote]
The more tools we have in our toolbox, the more choices we have to implement functionality. As long as they're written well, we can pick the right tool for the job.
Besides, AFTER triggers already exist, so aren't BEFORE triggers just logical?