Re: Stored Procedure vs ESQL/C

Gooday Frank, I have found that stored procs are best kept short and sweet. They are great for referential integrity (called by triggers) and they are great for enforcing business rules. I have seen them used to write batch jobs because the language syntax is relatively simple (a very valid reason). However they do not seem to be optimised for mathematical operations and they do not have the ability to buffer inserts with the "put" statement (at least in any version I have seen). If you have a complex task to perform, particularly if it involves a lot of inserts, you will probably get it to run a lot quicker using esql/c. HTH, Pete Harris, ComputerShare Systems. "Catrine, Francis" <Francis.Catrine@fmr.com> wrote in article <61ll32$717@cssun.mathcs.emory.edu>... > Does anyone have any experience / testing results that > show the difference in performance between stored procedures > and esql/c? > > IHAC that uses large stored procedures, and I am curious if using > esql/c called from the procedure would process faster. > > Thanks in advance, > > Frank C. > > Frank Catrine > Director, Informix Services > The Ross Group > >