Embedded SQL Performance

["Mike Naughton" <mnaughton@xxxxxxxxxxxx>]

Hi Everyone,

Does anyone have any tips on how to optimize performance of embedded SQL.
My application is basically a subfile lookup screen, and I use the SQL to
get all the data I need to fill the subfile before loading it. The screen
is read-only, so I'm not doing any updates or inserts or deletes, and I
retrieve a relatively small (but variable) number of rows (say less than
100).

I've  been reading the manual, and it seems to offer seveal options, but
I'm curious which ones are most effective. Should I bother with
"insensitve" and/or "read only" in the cursor declaration. How about using
"fetch n rows"? And if I use "fetch n", is it better to have n be my page
size, or should I try to have it large enough so that it will get
everything?

I figure the real answer is "it depends", but I'm curious if anyone else
has experimented with this.

Thanks!

Mike Naughton
Senior Programmer/Analyst
Judd Wire, Inc.
124 Turnpike Road
Turners Falls, MA  01376
413-863-4357 x444
mnaughton@juddwire.com

+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---