Re: Triggers (and I don't me Roy Rogers' Horses)

["Joe Teff" <jteff19@xxxxxxx>]

>Well, we're finally going to use some triggers on our system.
>We're concerned about the overhead of running the little monsters
> - Where does the overhead show up?  The job that kicks off the
>Trigger?  The subsystem?  The OS (as part of QDBSRV?)?
> - Is there a convenient place to monitor for the additional load?
>If anyone can provide a 25-words-or-less answer, or point me at the Right
>Fine Manual, I'd be greatly gratified.

I have used triggers quite a bit. I return with LR off so the trigger stays
loaded until the job ends. It is such a comfort to know that the exact
same business rules are applied every time to your database, especially
when DBU, DFU or remote (including Client/Server) access to your
database occurs. I have not noticed any performance degredation from
triggers at all. I can only think of one situation where a trigger has
noticably
slowed response, but that was a situation where hooks were put into an
existing system to interface to a new financial system. The response was
due to the amount of code and volumne of I/O that occurred in the trigger.
It was not the triggers fault, the work had to get done and the requirements
stated that it had to be done real-time.

Joe Teff


+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---