RE: SQL Update in RPGLE.

The HLL advantage comes from being able to rapidly get access to a record in
a table.  The real issue here is "what is a transaction".  If the
transaction involves a great deal of file IO, then SQL will probably
outperform native access.  However, if the transaction requires the
retrieval of a small, optimized set of records that can be accessed randomly
(by key), then native access would probably perform better.

There's no doubt that SQL can outperform native in many circumstances, but
there's no guarantee that this is always the case.  The DB2 developers have
done a great job of optimizing SQL over the last few releases, and it's
harder to make sweeping generalizations about native IO being faster than
SQL...

Eric DeLong
Sally Beauty Company
MIS-Project Manager (BSG)
940-297-2863 or ext. 1863



-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx]On Behalf Of Jake M
Sent: Friday, March 31, 2006 9:10 AM
To: RPG programming on the AS400 / iSeries
Subject: Re: SQL Update in RPGLE.


I am glad the horse ain't dead, yet!! Here is a thought and please feel free
to correct me but isn't the DB2 optimizer responsible for finding the most
optimal access path after the SQL statements are handed over to DB2. What I
am trying to get at is instead of making sure what the most efficient way of
data retrieval in RPGLE is you can just throw in a SQL statement and let the
DB2 optimizer figure out what is the best access path. Am I right? I am new
to RPG so I may be totally wrong but just a thought....

Cheers,

Jake.

On 3/31/06, Tom Huff <tehuff@xxxxxxxxxxxxx> wrote:
>
> I still don't think the horse is dead.
> Tom
>
>