![]() ![]() The trace facility can be turned on and off. Not a problem! Toad for Oracle retrieves and displays the trace file contents after the SQL is done executing. a developer does not have access to this trace file or may not even know the name of the trace file. The trace is created in a subdirectory where the Oracle software is installed. SQL Trace allows for the SQL statements that are contributing to the wait event time to be captured. When there is a performance issue, the DBA often looks at tools like AWR (automated workload repository Toad for Oracle DBA edition also has a nice interface to this data) and can see the wait events that are keeping the Oracle database busy. The trace file also includes the wait events, or the work that the SQL statement has asked Oracle to do. The SQL Trace includes all related information such as various timings (execute, fetch), row counts, total run times and more. ![]() The trace file collects SQL statements as they are submitted for execution to the Oracle RDBMS. Toad for Oracle has great support for this trace file. Within the scope of SQL performance tuning, SQL Trace has been around for a very long time. This blog, and related articles around using Toad for Oracle Expert Edition and Toad for Oracle DBA Edition will highlight the usefulness of Toad for Oracle for SQL performance tuning. Based on my experience, I believe that Quest ® Toad ® for Oracle is the best SQL Trace analysis tool for SQL performance tuning. ![]()
0 Comments
Leave a Reply. |