
78
|
Toad Pocket Reference for Oracle
After Debugging
When you complete a debugging session, there is one final
step you need to perform in order to clean up the Debug-
ger’s symbol table. Toggle off the “Toggle compiling with
debug” button and compile your stored program once more.
It will now recompile without the debug symbol tables. This
is especially important on production systems as the debug
symbols can adversely affect your code’s performance.
Code Profiling
Code Profiling is an extremely powerful tool that can be used
by developers to identify bottlenecks and code execution
problems. Toad uses the Oracle Probe Profiler API to collect
performance data on PL/SQL applications. This feature is
included in the Toad for Oracle Standard Edition. To use
this feature, you must first verify that you have the DBMS_
PROFILER package (created by Oracle’s PROFLOAD.sql
script). Then use Tools
➝ ServerSide Object Wizard to cre-
ate Toad’s Profiler tables.
Toggle Database
➝ PL/SQL Profiling on and then execute
your stored program. The Profiler prompts you to name each
run (execution). As each run completes, the Profiler Analysis
window displays performance data for each line of code.
Because this information is stored in database tables, you will
be able to run ad hoc queries and customize your own
reports. The reports will be viewable from the menu (shown
in Figure 17) invoked from Database
➝ Profiler Analysis.
Using ...