Re: Triggers & Stored Procedures

I am no major expert, but here is my take. It is better in general to separate SQL from the application, this way you could use diferent frontends calling the same Triggers / Procedures. The SQL in a procedure is already "compiled" and therefore does not be parsed again - better performance. If the procedure is performing a lot of heavy duty (non-SQL) mathematical type work, this may be an overhead on the server and you may want to perform this in the client. Experts, feel free to flame me! >Hi, Is anyone out there using triggers and stored procedures in Informix >for performance reason? Can someone identify the pros and cons of using >them? Our system is a web application (on NT) accessing Informix >database (on Unix). We are thinking about using the triggers may save us >time on passing the SQLs over the network to the Informix engine. The >Informix manual describes that we use triggers for audit trail or to >minimize redundant code in applications but does not mention anything >about performance.