From: sfitzgerald@centurytel.net (Sean Fitzgerald)
Newsgroups: comp.databases.oracle.server
Subject: Re: Auditing on using indexes
Date: 8 Aug 2001 13:55:52 -0700
Organization: http://groups.google.com/
Lines: 7
Message-ID: <605a2fd5.0108081255.74f4d1d5@posting.google.com>
References: <9kricm$t383@imsp212.netvigator.com> <9krlip$67ebi$1@ID-85580.news.dfncis.de>
NNTP-Posting-Host: 216.0.139.130
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-Trace: posting.google.com 997304152 6867 127.0.0.1 (8 Aug 2001 20:55:52 GMT)
X-Complaints-To: groups-abuse@google.com
NNTP-Posting-Date: 8 Aug 2001 20:55:52 GMT


The index tuning part of the expert package in Enterprise Manager
essentially does the same thing.  It samples your sql area and stores
all the sql statements it finds and then looks at all your indexes and
sees which ones are not used.  It might actually work if you feel you
can get a big enough sample to insure you are capturing all your sql. 
If you don't sample for long enough you might miss sql that is only
run weekly or monthly.