Subject | Trigger question |
---|---|
Author | Nico Callewaert |
Post date | 2009-08-25T22:49:34Z |
Hi list,
I was wondering if lots of triggers are slowing down the database. Let's say I have 500 tables and every table has 1 or more triggers associated with it. I guess every table operation has to locate the trigger it needs to execute ? Would this locate operation slow down when it has to choose from a list of 500+ triggers compared to less triggers ? I use these triggers to save current user and current timestamp for each record. But that means 500 tables is at least 500 triggers, so I was wondering if that is a good idea at all ?
Many thanks in advance,
Nico
[Non-text portions of this message have been removed]
I was wondering if lots of triggers are slowing down the database. Let's say I have 500 tables and every table has 1 or more triggers associated with it. I guess every table operation has to locate the trigger it needs to execute ? Would this locate operation slow down when it has to choose from a list of 500+ triggers compared to less triggers ? I use these triggers to save current user and current timestamp for each record. But that means 500 tables is at least 500 triggers, so I was wondering if that is a good idea at all ?
Many thanks in advance,
Nico
[Non-text portions of this message have been removed]