|
<snip> I would bet that any quick-running SQL statement can be made to run just as fast or even faster using RPG. </snip> I would disagree with you there. Set at a time operations are going to run faster. SQL is doing everything at the machine level. RPG has to be slower. It has to pull every record up through all the logical buffers. Even using READ instead of READE it has to be slower. SQL can do all kinds of optimizations at the machine level and IBM has gotten a lot better at optimizing queries. Anytime I am doing any kind of set operations (Sum, group by, update a lot of records, etc), I will always use SQL. The hassle with SQL is not having free-form SQL and the ugly way SQL is implemented in RPG. Only thing that keeps me from using it for everything.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.
midrange.com
