SQL Navigator for Oracle 7.4 - Installation Notes

PL/SQL Profiler

Analyze the execution time and efficiency of your stored programs. The Profiler is particularly useful for finding bottlenecks in stored code and quality assurance and testing.

Toolbar

Icon	Tool Tip	Description	Keyboard Shortcut
	Refresh	Update both Run and Group tree views with the latest profiling data.	Alt+R
	Filters / Preferences	Open the Profiler Filter/Preferences Dialog. You can sort and filter the result data according to thresholds that you set. This makes it easy to limit the amount of data displayed, and to isolate the most significant items. For example, you can select lines that were not called during the run, or runs with total times higher than average.	Alt+P
	Delete	Delete the data for the selected run. If a group is selected then delete the group. Removing the group does not remove the associated run data.	Del
	Create New Group	Create a new group. Open the New Group / Group Properties Dialog. Create groups to logically connect code units and runs. You determine which units and runs belong to a group. You can combine data for a single code unit across multiple runs in order to determine the real coverage and execution times. This is useful when testing stored code in several different runs with different parameters.	Ins
	Locate the selected object in DB Navigator	Open DB Navigator with the tree expanded to highlight the selected object. See where the object is in the database tree.
	Open the selected object	Open the selected object in the Code Editor. Select a line of source code in the Source Viewer tab to open the Code Editor at that line.
	Properties	Open the New Group / Group Properties Dialog to modify the selected group.	Alt+F2
	Launch Xpert tuning	Open SQL Optimizer for Oracle.

Runs Tab

A run contains all code units that are called during execution. If a procedure or function is a part of a package, the whole package becomes part of the run. The same rule applies to type methods.

Groups Tab

For each group, you have the option of displaying the data either separately by run, or with runs combined.

Select PL/SQL Code on the Runs or Groups Tab

A PL/SQL code unit can be a stand-alone procedure or function, a package body, a type body or an anonymous block. A package body and type body contains further procedures and functions. For a procedure or function, it is sometimes possible to determine how many times it has been called during a run by parsing the available source code and combining the data about the lines where the procedure/function is called.

The Profiler will show you a line-by line analysis of the execution, including the number of times each line was executed and the time required for execution.

The Profiler:

• stores data about each code unit executed during a run, down to the level of source code lines
• divides all the available profiling data into hierarchically organized logical items
• displays profiling and coverage statistics about each item and compares them with others

The Profiler displays the profiling data alongside the actual source code. (This feature is not available if the source code has changed since it was last tested in the currently selected run, or if it is not identical across the runs in a group.)