×
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.
In regard to the performance of SQL vs. RLA, perhaps the most relevant fact
is that the SQL Query Engine uses RLA under the covers. Not the same QRNXIO
procedure calls that are made when invoking RPG I/O opcodes, but a
comparable RLA API. A number of IBM i components use the RLA API exported
from the QC2IO service program, but I haven't taken the time to see what is
used by SQL programs.
In the event that an SQL query outperforms RLA code, then it was probably
due to some misguided or bone-headed thought process on the part of the
programmer. Maybe he was using program joins rather than an external join
provided by a logical file.
The SQL query engine always adds overhead while attempting to figure out an
optimal access methodology, to perform mapping between DB record buffers
and cursors.
The justification for SQL is convenience. It can do a lot under the covers
that would otherwise require a lot of code. The justification for SQL is
programmer productivity - not performance.
As an Amazon Associate we earn from qualifying purchases.
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.