× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



This is a recap of the old RPG vs. SQL performance issue. As far as I
remember, inserting records with RPG is far more efficient than doing
multiple SQL INSERTs (40 times?) The reason is, if the connection is not
closed between the inserts, RPG stored procedure can keep the file open (it
can even be buffered with a large block factor), whereas SQL cannot. Hence
the difference.

Lo

> -----Original Message-----
> From: Jerrold_Bisera@countrywide.com
> [mailto:Jerrold_Bisera@countrywide.com]
> Sent: 09 October 2002 02:20
> To: java400-l@midrange.com
> Subject: Stored Procedure or Prepared Statement
>
>
> This is a multipart message in MIME format.
> --
> [ Picked text/plain from multipart/alternative ]
> Is there a performance difference between using a prepared
> statement vs
> stored procedure call when doing multiple inserts in a
> database file?  The
> java code executing the prepared statement or the stored
> procedure resides
> on the same machine.
>
> Jerrold Bisera
> --
>
> _______________________________________________
> This is the Java Programming on and around the iSeries /
> AS400 (JAVA400-L) mailing list
> To post a message email: JAVA400-L@midrange.com
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/cgi-bin/listinfo/java400-l
> or email: JAVA400-L-request@midrange.com
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/java400-l.
>


As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.