Re: SQL index possible with keys from two tables?

Elvis,

There's no chance an index will be used for ordering when the ORDER BY

contains columns from more than one table. So, you're out of luck trying to
tune that part of the query.

Hence my original thread question (see the subject line). Interestingly, if
MQT's on the i supported Refresh Immediate (and they don't at least at my
V5R4 level), it seems you actually could do this. For my invoice file,
which only changes during day-end processing, the Refresh Deferred is just
fine and creating an index over the MQT does in fact give me an index from
more than one table. (You can even use it for RLA just as you would a LF.)
For the orders file, which changes constantly, the Refresh Deferred is less
ideal.

But still glad I asked, because somehow I had missed the whole concept of
MQT's previously. In some contexts, particularly summary queries, I can see
them as being potentially VERY useful.

Doug