re: SQL vs. traditional I/O?

I asked this question some time ago.
The answers I got were not convincing to do the switch.
So I stayed traditional for some time.

Eventually we upgraded to a new version of software that used
SQL.  I made an effort to learn SQL.
The packaged software did not use SQL to its full potential but
I kept at it till I got a grasp of ALL SQLs functions.
The end result is I rarely use Trad I/O.

There is no need to retrofit SQL to your old RPG code, in fact it
is a mistake to do this (IMHO).

Once you use SQL you will also need to understand how to tune
the database. Basically it means creating the appropriate LGL
files (SQL indexes) to help the DB optimiser get at the data faster.
(refer to STRDBMON PRTSQLINF)

SQL is a powerful tool. I like to say sure you can do a fine job
with a hand saw but I prefer my powered circular saw.

Frank Kolmann