Results 1 to 4 of 4
  1. #1
    Join Date
    Aug 2002
    Location
    Chennai, India
    Posts
    184

    Unanswered: Pitfalls to avoid for use of Triggers in V7

    Triggers can improve performance. However, are there any known pitfalls to avoid?

    What is the overhead of using a Trigger like an audit tool for moving the 'old image of records changed' to another table before UPDATE?

    TIA.

  2. #2
    Join Date
    Jun 2003
    Location
    Toronto, Canada
    Posts
    5,516
    Provided Answers: 1
    Quote Originally Posted by ggnanaraj
    Triggers can improve performance.
    Are you sure about that?

  3. #3
    Join Date
    Aug 2004
    Posts
    330
    One thing to think about when considering using a trigger: If the trigger is NOT used, then the audit may have to be done by the application. If you require that an audit trail be kept, then why not used a trigger? Can the application perform better than the DBMS? Without the triggers, there will be ways to circumvent the audit by using ad-hoc queries to get to the data.

  4. #4
    Join Date
    Aug 2001
    Location
    UK
    Posts
    4,650
    Please note , you cannot 'move' a old row into another table as part of BEFORE trigger .. You'll have to use the AFTER Trigger OLD ROW ..

    Sathyaram

    Quote Originally Posted by ggnanaraj
    Triggers can improve performance. However, are there any known pitfalls to avoid?

    What is the overhead of using a Trigger like an audit tool for moving the 'old image of records changed' to another table before UPDATE?

    TIA.
    Visit the new-look IDUG Website , register to gain access to the excellent content.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •