RE: sqlrpgle select statements

Jon,

I did that and if it was called in batch (like through Ops-Nav or from a
remote machine), it used the logical it was supposed to. If called
interactively, it would do full table scans every time. Not cool on 60
million+ row tables. The optimizer messages we got said to create an
index exactly like the ones it wouldn't use. I spent lots of time trying
to make this work and until I changed the compile setting, it didn't. My
guess is that it had something to do with either the environment it was
running in (JD Edwards World) or with how the files are defined (files
with CCSID 37 and data with CCSID 65535) but changing either of those
wasn't an option.

Matt

-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Jon Paris
Sent: Wednesday, March 01, 2006 4:05 PM
To: rpg400-l@xxxxxxxxxxxx
Subject: RE: sqlrpgle select statements

 >> I've run into cases where logicals that exactly matched the where
and
order by clauses were not used. 

Run the program in debug or simply key the select into Op-Nav and have
it
analyze the SQL.  Just because there is an apparent exact match in a
logical
does not necessarily mean that it will be the fastest access route.  The
debug statements in the Job Log will show you _why_ the query optimizer
rejected the path in question.


Jon Paris
Partner400

www.Partner400.com
www.RPGWorld.com 
-----Original Message-----