I agree generally to go ahead and create the thing. However, it might not be used directly - it might be used to determine that it is not the best way to retrieve the data, to determine that another access plan is the best idea. Visual Explain usually has pretty good explanations for the choices the optimizer made.


On 3/14/2012 12:37 PM, Gord Hutchinson wrote:
Thanks Jim. We're still only on V5R4.


On Wed, Mar 14, 2012 at 12:26 PM, Jim Oberholtzer<midrangel@xxxxxxxxxx>wrote:


I would trust the adviser. The cardinality on that table is about 10%
so my own thought is you should be good to go.

Updates should not be an issue. V5, V6 or V7?

Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects

On 3/14/2012 10:21 AM, Gord Hutchinson wrote:
How reliable are the Index Advisor recommendations for creating an EVI?

I have a table which last Saturday had 622,804 rows with 60,922 distinct
values of the key field for which the advisor is recommending an EVI.
Currently there are 61,752 distinct values out of 635,428 rows.

This table grows by 20K to 30K rows per week. There are also lots of
updates and deletes to the table.

This seems like a lot higher number of distinct entries than I've seen
recommended for an EVI.


-- Gord Hutchinson TST Overland Express
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

This thread ...


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

This mailing list archive is Copyright 1997-2020 by midrange.com 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].