AW: IGNORE_DERIVED_INDEX

The recommendation is to use IGNORE_DERIVED_INDEX *YES and create all your
logical files (except the join logical files) as SQL indexes.
With release 6.1 it is possible to create derived and sparse indexes which
allow to create new columns, define keys over these new columns and add
where clauses to an index.

Because SQL indexes can be used with native I/O like any keyed logical file
and indexes can be used by the SQE, there is no need to create and use
logical files with select/omit clauses.


Mit freundlichen Grüßen / Best regards

Birgitta Hauser

"Shoot for the moon, even if you miss, you'll land among the stars." (Les
Brown)
"If you think education is expensive, try ignorance." (Derek Bok)
"What is worse than training your staff and losing them? Not training them
and keeping them!"


-----Ursprüngliche Nachricht-----
Von: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] Im Auftrag von rob@xxxxxxxxx
Gesendet: Monday, 14. February 2011 17:21
Betreff: IGNORE_DERIVED_INDEX

What is the recommendation for "IGNORE_DERIVED_INDEX" in the QAQQINI file?
We are running 8.3 03 of Infor LX on IBM i 7.1.

I noticed that the 6.1 Memo To Users has this:
QAQQINI option changes
In V6R1, the default value for the QAQQINI option for IGNORE_DERIVED_INDEX
has changed from *NO to *YES. The default behavior now runs supported
queries through the SQE even if a select/omit logical file index is
created over any of the tables in the query. In V6R1, the SQE optimizer
supports many types of derived indexes. The usage of the QAQQINI option
for IGNORE_DERIVED_INDEX applies to only select/omit logical file indexes.


Rob Berendt