This is the only known detractor I have seen to making the switch. CQE can
use keyed S/O LFs and since in BPCS keys queries were written with these S/O
LFs in mind, they're tightly integrated and perform well. SQE cannot use S/O
LFs and even if an equivalent full sql index exists, it won't perform as
well (it'll come close). If you don't build full sql indexes (or non-S/O
keyed LFS) though, CQE will beat the pants off of SQE, since SQE will have
to default to table scans in that case.

That said, IGNORE_DERIVED_INDEX is a default on V6R1 and I have seen many
fantastic results on customers machines. One guy even got a promotion after
he made the switch (no kidding; system performance went up dramatically and
CPU usage dropped dramatically).


Celebrating 11-Years of SQL Performance Excellence on IBM i, i5/OS and

-----Original Message-----
Subject: Re: CQE, SQE and QAQQINI

Would it concern you that a major software house sides with your boss?

SQL Performance
Affected BPCS versions: V6.x, V8.x
Infor recommends the following QAQQINI file setting to
be activated for support with R610:

The BPCS and ERPLX database contains large numbers of
Select/Omit logical files and if this option is not set,
these logical files will be ignored when the SQL Optimzer
selects logical files to run a given query. This can cause
poor performance.

The following command shows how to setup this option...

Rob Berendt

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 by and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].