RE: Using the Index Advisor

I think it still happens (not that I look for it any more, I've learned to
live with redundant index advice).
If that's truly the case here, there's really nothing he can do about it.

One piece of good news in relation to this is that with V6R1 we'll be able
to create sparse indexes which SQE can use (kind of like CQE can use keyed
Select/Omit LFs today). This will alleviate this problem to some degree as
we'll be able to tie the index more tightly with the query we want to tune.

By no means will it alleviate all of the quirks. It's just the nature of the
beast.

Elvis

Celebrating 11-Years of SQL Performance Excellence on IBM i5/OS and OS/400
www.centerfieldtechnology.com


-----Original Message-----
Subject: Re: Using the Index Advisor

Mike

Sometimes in the past - Elvis could say more about present situation - the
index was asked for when you had nested or common table expressions, or
views based on views - that kind of thing. But by the time the access plan
works with the file, it is working with a copy - and it really wants an
index over the copy. So your logical is not even considered anymore.

Elvis, do you still see this behavior? I might not know the exact way it
works, but it seems we used to see this.

HTH
Vern