Pitfalls to avoid for use of Triggers in V7

ggnanaraj · #1 (**permalink**) 12-09-05, 07:12

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.

n_i · #2 (**permalink**) 12-09-05, 08:47

Quote:

Originally Posted by ggnanaraj

Triggers can improve performance.

Are you sure about that?

urquel · #3 (**permalink**) 12-09-05, 09:47

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.

sathyaram_s · #4 (**permalink**) 12-09-05, 13:18

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.

Internet Services

Web Development

Digital Marketing

Consumer Tech