TRIGGER FOR UPDATE is getting big

  • I'm working on UPDATE TRIGGER

    It's getting more than 200 lines.

    It has 4 IF UPDATE() checks

    and each IF UPDATE() check

    has two INSERTS.

    I started worrying about performace.

    Because the TRIGGER is now pretty big.

    Anybody had any performance issues due to

    big TRIGGERS?

  • Sounds big, but it really matters more how long it takes and what the possibility is that the code executing will get blocked by someone else. Definitely worth stress testing a little. How about posting the code, maybe we can offer suggestions.

    Andy

    http://www.sqlservercentral.com/columnists/awarren/

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

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