• noeld (2/3/2009)


    Actually I have had the need for this feature for a long time.

    Suppose you need to prevent changes on ONE table while you are doing some maintenance work in a Db.

    To Set a DB in read-only mode is too drastic, To Setup that table in a separated File and make it read only is inconvenient.

    To setup INSTEAD OF/AFTER TRIGGERS is expensive in Server resources.

    This solution seems cheap and Fast 😉

    It seems expensive to me, re-ednabling the clustered index implies rebuilding every index on the table. If the DB design is reasonable, there are a maybe a small number of roles which have permissions on this table - altering those permissions seems pretty cheap and easy (and also provides the option of making the table read only, which is a little less drastic than making it completely inaccessible - particularly if your objective is, as you suggest, just to prevent changes).

    Tom