• john.yori 32529 (5/6/2015)


    Hi we have a legacy application running on sql2005. We suspect part of our performance issues is from the table triggers being fired so Development wants me to see if I can tell them how often the triggers in the database fires.

    I cannot find anything and was hoping someone could give me some tips.

    NOTE: I have Spotlight if anyone knows how to get it out of there that will work as well.

    Are the performance issues having to do with INSERTs, UPDATEs, or DELETEs? If not, then it has nothing to do with the triggers.

    It would be helpful to you if Dev identified where they are having a performance issue and leave finding out "why" up to you.

    --Jeff Moden


    RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
    First step towards the paradigm shift of writing Set Based code:
    ________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

    Change is inevitable... Change for the better is not.


    Helpful Links:
    How to post code problems
    How to Post Performance Problems
    Create a Tally Function (fnTally)