Other than benchmarking the various business process(es) your
application supports and comparing before and after performance, no. If
you improve SELECT performance for a query that runs once a day during a
nightly batch process that no one cares how quickly it returns and cut
daytime OLTP performance 10%, that is probably a bad index. If you
improve a critical query and slow down a lower priority process, that's
probably a good index. Without assigning some sort of business value to
the affected processes, you can't draw many conclusions.

David Aldridge had an excellent discussion on this

http://oraclesponge.blogspot.com/2005/04/response-times-what-user-thinks
-and.html

Justin Cave
Distributed Database Consulting, Inc.
http://www.ddbcinc.com/askDDBC

-----Original Message-----
From: Deepak Panda
[mailto:oracledba-ezmlmshield-x5734272.[Email address protected]
Sent: Saturday, June 04, 2005 1:25 AM
To: LazyDBA Discussion
Subject: Index & Performance

Hi All,

We have few queries whose performance gets enhanced by creating an index
on a particular table. But how to asses whether the overall performance
of the application has increased in general. As addition of the new
index may cause slow updation on that column. Is there any rule of thumb
for determining the same?

Please give your inputs.

Regards

Deepak


--------
website: http://www.LazyDBA.com
Please don't reply to RTFM questions
Oracle documentation is here: http://tahiti.oracle.com
To unsubscribe: see http://www.lazydba.com/unsubscribe.html
To subscribe: see http://www.lazydba.com
By using this list you agree to these
terms:http://www.lazydba.com/legal.html


Oracle LazyDBA home page