Dictionary traps   Although it's not well-known yet, many statistics of child(recursive) statements are included in their parent's statistics. If you query dictionary views directly, you may fall in this trap. This may distort your measurements and decisions. Here is a sample for PL/SQL statement which inludes an INSERT statement: Parent PL/SQL statement: BEGIN pdoug; END; Child(recursive) statement: INSERT INTO DOUG VALUES ( :b1,:b2 ) select SQL_TEXT,DISK_READS,BUFFER_GETS,ROWS_PROCESSED from v$sql where upper(SQL_TEXT) like '%DOUG%'; SQL_TEXT DISK_READS BUFFER_GET ----------------------------------- ----------- ----------- INSERT INTO DOUG VALUES ( :b1,:b2 ) 3533 138083 BEGIN pdoug; END; 3533 138083 As seen above, the statistics are reported twice for both statements. This distortion can be occur on any statements if statements call any other statements such as triggers, functions, internal Oracle statements, etc. Any scripts, any tools which get values directly from Oracle dictionary may fall in this important, but not well-known measurement problem. itrprof SQL Analyzer can report both cumulative and exclusive statistics without distorting any statistics.   Web based   itrprof is a web based tool. Yo don't have to install anything on your clients. Installing and upgrading are very easy.   Fast   itrprof SQL Analyzer can read trace files in ZIP(.zip) and GZIP(.gz) formats. itrprof SQL Analyzer sends compressed analysis results to HTTP/1.1 enabled browsers. Then, browsers de-compress reponse on the fly. itrprof SQL Analyzer doesn't save trace files to server. Trace files are processed in the memory-efficient data structures ON-THE-FLY while you post your trace files. itrprof SQL Analyzer uses its own data structures such as Hash, Tree, List, etc. It doesn't use any database. itrprof SQL Analyzer is a web based Java Servlet application. Java Servlet technology is faster than other technologies such as CGI.   Response time based   itrprof SQL Analyzer uses Response Time Performance Modeling. In other words, itrprof SQL Analyzer uses the best performance modeling for performance problems.   Security   SQL_TRACE and Event 10046 trace files don't include CONNECT statements. That means your username/password in CONNECT statements are not included in SQL_TRACE and Event 10046 trace files.   Expertise   You don't have to be a performance expert to find your bottlenecks. itrprof SQL Analyzer can do it for you. You can find the cause of any level performance problems in minutes.   Event 10046 trace files   Event 10046 trace files are one of the best available sources for Oracle tuning. It includes many statistics to tune Oracle.   Trace file traps   There are a lot of traps in Event 10046 trace files. Interpreting trace files by simple scripts may cause very erroneous results. itrprof SQL Analyzer with the source code of around 6.500 lines reports accurate analysis results.   Others   The product features table shows the overall feaures of itrprof SQL Analyzer.