Comments on: What Did My New Index Mess Up?

By: osborne

osborne — Mon, 20 Jul 2009 13:14:15 +0000

Thanks for the comments guys. I have been using this one quite a bit lately. I find I often change it to pivot around a specific snap_id. Like add an index at 11:05, find the 11:00 snap_id, and use that as my pivot point. I also find myself reducing the default minimum etime and minimum stddev parameters. It does turn up some interesting information. Thanks again for all the positive comments.

Kerry

By: Hemant K Chitale

Hemant K Chitale — Mon, 20 Jul 2009 09:32:20 +0000

Great Script !

It is worthy of sharing at a Conference !

By: Anand

Anand — Sat, 04 Jul 2009 21:46:10 +0000

Great script…Nice work..Waiting for more

Regards,
Anand

By: Blogroll Report 26/06/2009 – 03/07/2006 « Coskan’s Approach to Oracle

Blogroll Report 26/06/2009 – 03/07/2006 « Coskan’s Approach to Oracle — Fri, 03 Jul 2009 15:29:17 +0000

[...] Kerry Osborne – What Did My New Index Mess Up? [...]

By: Mark Davidson

Mark Davidson — Mon, 29 Jun 2009 13:22:24 +0000

Kerry,

Excellent script and thank you! This type of script will be extremely helpful in finding those “little” queries that seem to go bad after a release when the development team forgets to let the DBA’s know something else was changed and also when the DBA’s may have missed something.
This might be a good presentation for Hotsos 2010… something like to “Tools and Methods for Identifying Post-Release Issues” :-)

Thanks again,
Mark

By: B. Polarski

B. Polarski — Mon, 29 Jun 2009 12:04:40 +0000

Nice piece of work. Couple it with the Z. Breitling published in 2006 ‘http://www.doggarts.com/sql/xplan.sql’ and you get a powerful monitoring and diagnostic tool:
Your query pinpoint candidates to investigate plan variance.

By: alex

alex — Fri, 26 Jun 2009 21:47:48 +0000

Hi Kerry,

I think the script is very good and can help a lot in those so called “post release - it should be faster the dev team told me ” situations. Excellent work !

Regards,
Alex