Editor Profiler Tab
Within the Editor, the Profiler tab displays profiler runs, as root nodes, and profiler units as child nodes. The latter are the actual code units that were executed during a profiler run. They can include anonymous blocks, procedures, functions, and packages executed while the profiler run data was being collected. In the line item profiler, child nodes contain the actual line data. In the hierarchical profiler, child nodes contain sub program calls.
This tab provides an overview of the data, but does not offer the graphs that the Profiler Analysis window does.
Selecting a line item within the nodes automatically opens the referenced SQL source and displays the line referenced by the profiler.
Note: Because each Editor tab is associated with a separate Profiler instance, navigating through your code this way may reset the node display in the Profiler tab.
To display the Profiler Analysis window for the current data
Click Details.
Executable Line Indicators
When you open a profiler run or unit into the Editor and have the option show executable line indicators in gutters selected, executable line indicators display as follows:
|
Indicator |
Meaning |
|---|---|
|
Blue dot with green square |
Line was executed |
|
Blue dot with red circle |
Line was not executed |
If Toad cannot determine when the unit was last executed, then the standard blue dot line indicators will display.
You can filter the results of your hierarchical profiling session. This can be useful in making sure that you only see the results that are useful for you.
Toad will automatically filter out the system information that is added when the profiler is active. You can manually turn these on if you want to see that information.
To create a filter
- From the Profiler tab at the bottom of the Editor, right click the grid and select Filter.
Note: If you do not see the filter option, make sure you are actually using the hierarchical profiler.
- Click Add to add a new filter to the filter grid. Enter the criteria you want to use to hide data. You may use the % wildcard within the filter.
- Enable or disable any filters desired by selecting or clearing the Enable box.
- Repeat steps 2 and 3 if necessary.
- Click OK.
Generate Explain Plans
Toad provides an intuitive and efficient way to write, run, and test your SQL and PL/SQL code. Toad supports efficient code management for a single developer or a whole team of developers.
Generate Explain Plans
Tip: Click 
Save Explain Plans
You can save explain plans automatically in Toad or manually save them as an external file. The first option allows you to compare a current or historic Explain Plan to the saved file in the future.
To save Explain Plans automatically
- Select View | Toad Options | Oracle | General.
- Select Save previous Explain Plan results.
To save Explain Plans to an external file
- Run an Explain Plan.
-
Right-click the plan and select Save to XML file or Save image.
Note: To open an XML explain plan, right-click the Explain Plan area and select Load plan from XML.