RE: SQL vs native access (was: Record name the same as the filename)

[rob@xxxxxxxxx]

Not it wasn't incomplete enough to be misleading.  The point was that for 
the type of operation being performed, the SQL access was faster than the 
native access.  And the point further being that the person chose to 
remain with Native.  Why?  Because it was their personal comfort zone. 
Even though they designed and ran the time trials.  Granted, this was the 
same individual who converted 
C                      IF    (factor1>factor2) and (factora=factorb)
back into the dark ages with
C      FACTOR1  IFGT   FACTOR2
C      FACTORA ANDEQ FACTORB


And to all, I understand what you are saying.  Based on your time trials, 
and your specific access, native may, or may not, be slower, faster, or 
comparable.  Just don't assume one way or another.  And if you like one 
way or another because that is your personal comfort zone, be honest about 
it and don't try to come up with a business reason to justify your 
personal preference.

ps:  Joe, a single row fetch does not need a SELECT/FETCH.  A simple 
SELECT INTO will suffice.

Rob Berendt
-- 
"They that can give up essential liberty to obtain a little temporary 
safety deserve neither liberty nor safety." 
Benjamin Franklin 





"Joe Pluta" <joepluta@xxxxxxxxxxxxxxxxx>
Sent by: rpg400-l-bounces@xxxxxxxxxxxx
08/21/2003 05:15 PM
Please respond to RPG programming on the AS400 / iSeries
 
        To:     "'RPG programming on the AS400 / iSeries'" 
<rpg400-l@xxxxxxxxxxxx>
        cc: 
        Fax to: 
        Subject:        RE: SQL vs native access (was: Record name the 
same as the filename)


> From: <rob@xxxxxxxxx>
>
> Another business case. A die hard native person did some time trials
and
> was stunned to find the sql faster. However he decided to stick with
> native anyway.

This is somewhat apocryphal, or at least incomplete enough to be
misleading.  For what type of operation was SQL faster?  And why did the
person stick with native?  Some people like to use native access because
they find it easier to debug 10 separate I/O statements than one
ten-line-long SQL statement.

In any event, my most recent comparisons still showed SQL being roundly
outperformed by native access for single-record chains and particularly
for single-record inserts and updates.  If you have other information,
I'd love to see it.  At the same time, I'll try to dig up those tests
and run them again.

Joe

_______________________________________________
This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.