Re: HowTo find out used (useful) and unused (usesless) indexes?

From: Shakespeare <whatsin_at_xs4all.nl>
Date: Sun, 20 Apr 2008 10:05:17 +0200
Message-ID: <480af934$0$14354$e4fe514c@news.xs4all.nl>

"DA Morgan" <damorgan_at_psoug.org> schreef in bericht news:1208624947.696580_at_bubbleator.drizzle.com...
> Shakespeare wrote:
>
>> But an index may become useful over time, true?
>>
>> Shakespeare
>
> On that basis alone one could justify putting an index on every
> column of every table so I will respectfully disagree unless you
> write a very broad definition of "may."
>
> You need to understand your data and how it is being accessed.
> The extra overhead of an unused index is not value added.
>
> My recommendation would be to use the DBMS_STATS.SET.... procedures
> to see how queries will react to the expected future growth of both
> tables and indexes.
> --
> Daniel A. Morgan
> Oracle Ace Director & Instructor
> University of Washington
> damorgan_at_x.washington.edu (replace x with u to respond)
> Puget Sound Oracle Users Group
> www.psoug.org

I was aiming at data with for example a 'year' column. This column could be indexed by design, but in the first year (all records same value) this index is not useful and won't be used. But on the first entry in the second year it is useful to find entries of that year and so on. A script to remove or disable unused indexes would remove/disable this index in the first year.

Shakespeare Received on Sun Apr 20 2008 - 03:05:17 CDT

Original text of this message