Over the years I have experimented with creating a custom performance tuning tool. Below are a couple screen shots of the program.
Part 2:
http://hoopercharles.wordpress.com/2009/12/13/toy-project-for-performance-tuning-2/
Charles Hooper's Oracle Notes
Miscellaneous Random Oracle Topics: Stop, Think, … Understand
Categories
Recent Articles
- Everything or Nothing in SQL
- Grouping Data Sets by Week Number of the Month
- Analysis Challenges
- Unexpected Timer Resolution, Unexpected Parked CPUs, Unexpected Power Consumption
- Value of Improving One’s Knowledge
- Bitten by a Virtual Column, _OPTIMIZER_IGNORE_HINTS Doesn’t Ignore Hints?
- What does it Mean when a Select Statement in Oracle is using 100% CPU?
- Feeling ANSI About Oracle Join Syntax? 2
- Send an Email From Excel, Visual Basic 6, or a Windows Command Line Using Oracle’s UTL_MAIL Package
- Connecting to an Oracle Database with Visual Basic 6.0 on Windows 8 64 Bit
- Name that Table’s Column
- oci-24550 [3221225477] [Unhandled exception: Code=c0000005 Flags=0
- Undo Quiz – Bringing the Right Tools for the Job
- On the Topic of Programming 3
- On the Topic of Programming 2
Misc. Articles
Popular Articles
- #01 Calculate the Distance Between Two Latitude/Longitude Points using Plain SQL
- #02 Deadlock on Oracle 11g but Not on 10g
- #03 Demonstration of Oracle "Ignoring" an Index Hint
- #04 How to Collect Statistics
- #05 Retrieve Data to Excel with a Macro using ADO
- #28 Book Review: Oracle Database 11gR2 Performance Tuning Cookbook (Part 1)
- #68 Book Review: Oracle Database 11g Performance Tuning Recipes (p2)
- #78 Book Review: Oracle Tuning: The Definitive Reference Second Edition
Blogroll
Expert Oracle Practices: Oracle Database Administration from the Oak Table
Hints for Posting Code Sections in Comments
********************
When the spacing of text in a comment section is important for readability (execution plans, PL/SQL blocks, SQL, SQL*Plus output, etc.) please use a <pre> tag before the code section and a </pre> tag after the code section:
<pre>
SQL> SELECT 2 SYSDATE TODAY 3 FROM 4 DUAL; TODAY --------- 01-MAR-12
</pre>
********************
When posting test case samples, it is much easier for people to reproduce the test case when the SQL*Plus line prefixes are not included - if possible, please remove those line prefixes. This:
SELECT SYSDATE TODAY FROM DUAL;
Is easier to execute in a test case script than this:
SQL> SELECT 2 SYSDATE TODAY 3 FROM 4 DUAL;
********************
Greater than and Less than signs in code sections are often interpretted as HTML formatting commands. Please replace these characters in the code sections with the HTML equivalents for these characters:
< < > >
Recent Comments