RE: When should one use SQL/RPG?

<snip>

Just to be clear, I am a big fan of embedded SQL for record retrieval.  It
just seems like a lot of overhead to possibly build and prepare a statement
or have the query engine do it's work for a single record.  Maybe I'm
misunderstanding how the system handles embedded SQL though.  Wouldn't be
the first time. :)

Rick
<snip>


Rick,

For a single record, SQL is less efficient than RPG since much of the same work 
(mostly running through the query optimizer) has to be done for both single 
record and multi-record result sets. Where SQL shines (as long as the files are 
properly indexed) is in doing bulk operations (like updating multiple records). 
SQL is also very good (and much faster than DDM files) when you are accessing 
data on remote systems.

Matt