• Jeff Moden - Saturday, May 20, 2017 2:33 PM

    I just posted a plea and a link to this post on "the thread".  I'd love to see "BEFORE Triggers" become a reality instead of those gosh-awful "Instead Of" triggers.  I have little love in general for Oracle but this one of those things that Oracle absolutely did right from the git.  It would make writing audit triggers a whole lot easier to prevent unnecessary duplication in audit tables, which become some of the biggest tables of them all.

    [/quote]

    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,


    Hugo Kornelis, SQL Server/Data Platform MVP (2006-2016)
    Visit my SQL Server blog: https://sqlserverfast.com/blog/
    SQL Server Execution Plan Reference: https://sqlserverfast.com/epr/