Single vs Multiple triggers on a table

  • Hi, can anyone give me an opinion on something I'm presently doing.

    I have a dynamically generated trigger that will be applied to a number of tables in a database.

    One of the things this trigger needs to do is record whether it was triggered by an update, delete or insert.

    Now there are two obvious approaches to this in my mind, firstly to have a single trigger invoked for all insert, update and deletes which will run three fairly simple updates for these three subsets of the inserted / deleted data.

    Or the other approach which would be to have three triggers per table each running their own update.

    As the updates themselves are not that complex, I feel the former approach may bring less of an overhead but I wonder if anyone who is more of an expert can share any experience in this respect.

    Best Regards,

    Mat Wood

  • My vote is for single trigger. becuase of performances and maintainance wise I think single trigger will do the job.




    My Blog: http://dineshasanka.spaces.live.com/

Viewing 2 posts - 1 through 1 (of 1 total)

You must be logged in to reply to this topic. Login to reply