Edit D:\app\Administrator\product\11.2.0\dbhome_1\oc4j\j2ee\oc4j_applications\applications\em\em\online_help\ratug\spa_intro004.htm
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en"> <head> <meta http-equiv="Content-Type" content="text/html; charset=us-ascii" /> <meta http-equiv="Content-Style-Type" content="text/css" /> <meta http-equiv="Content-Script-Type" content="text/javascript" /> <title>Measuring the Pre-Change SQL Performance</title> <meta name="generator" content="Oracle DARB XHTML Converter (Mode = ohj/ohw) - Version 5.1.1 Build 005" /> <meta name="date" content="2009-06-04T10:50:31Z" /> <meta name="robots" content="noarchive" /> <meta name="doctitle" content="Measuring the Pre-Change SQL Performance" /> <meta name="relnum" content="11g Release 2 (11.2)" /> <meta name="partnum" content="E12254-01" /> <link rel="copyright" href="./dcommon/html/cpyr.htm" title="Copyright" type="text/html" /> <link rel="stylesheet" href="./dcommon/css/blafdoc.css" title="Oracle BLAFDoc" type="text/css" /> <link rel="contents" href="toc.htm" title="Contents" type="text/html" /> <link rel="prev" href="spa_intro003.htm" title="Previous" type="text/html" /> <link rel="next" href="spa_intro005.htm" title="Next" type="text/html" /> <script src="./callback.js" type="text/javascript"></script> <noscript>Your browser does not support JavaScript. This help page requires JavaScript to render correctly.</noscript> </head> <body> <div class="zz-skip-header"><a href="#BEGIN">Skip Headers</a></div> <table class="simple oac_no_warn" summary="" cellspacing="0" cellpadding="0" width="100%"> <col width="86%" /> <col width="*" /> <tr valign="bottom"> <td align="left"></td> <td align="center"><a href="spa_intro003.htm"><img src="./dcommon/gifs/leftnav.gif" alt="Previous" /><br /> <span class="icon">Previous</span></a> </td> <td align="center"><a href="spa_intro005.htm"><img src="./dcommon/gifs/rightnav.gif" alt="Next" /><br /> <span class="icon">Next</span></a></td> </tr> </table> <p><a id="CHDBDHJF" name="CHDBDHJF"></a><a id="RATUG170" name="RATUG170"></a></p> <div class="sect1"><!-- infolevel="all" infotype="General" --> <h1>Measuring the Pre-Change SQL Performance</h1> <a name="BEGIN" id="BEGIN"></a> <p><a id="sthref42" name="sthref42"></a>Execute the SQL workload to create a pre-change SQL trial before making the system change. Executing a SQL workload runs each of the SQL statements contained in the workload to completion. During execution, SQL Performance Analyzer generates execution plans and computes execution statistics for each SQL statement in the workload. Each SQL statement in the SQL tuning set is executed separately from other SQL statements, without preserving their initial order of execution or concurrency. This is done at least twice for each SQL statement, for as many times as possible until the execution times out (up to a maximum of 10 times). The first execution is used to warm the buffer cache. All subsequent executions are then used to calculate the run-time execution statistics for the SQL statement based on their averages. To avoid a potential impact to the database, DDLs are not supported; only the query portion of DMLs are executed.</p> <p>Depending on its size, executing a SQL workload can be time and resource intensive. When executing a SQL workload, you can choose to generate execution plans only, without collecting execution statistics. This technique shortens the time to run the execution and lessens the effect on system resources, but a comprehensive performance analysis is not possible because only the execution plans will be available during the analysis.</p> <p>Alternatively, you can execute a SQL workload remotely on a separate database using a database link. SQL Performance Analyzer will establish a connection to the remote database using the database link, execute the SQL statements on that database, collect the execution plans and run-time statistics for each SQL statement, and store the results in a SQL trial on the local database that can be used for later analysis. This method is useful in cases where you want to:</p> <ul> <li> <p>Test a database upgrade</p> </li> <li> <p>Execute the SQL workload on a system running another version of Oracle Database</p> </li> <li> <p>Store the results from the SQL Performance Analyzer analysis on a separate test system</p> </li> <li> <p>Perform testing on multiple systems with different hardware configurations</p> </li> <li> <p>Use the newest features in SQL Performance Analyzer even if you are using an older version of Oracle Database on your production system</p> </li> </ul> <p>Once the SQL workload is executed, the resulting execution plans and run-time statistics are stored in a <a id="sthref43" name="sthref43"></a>SQL trial.</p> <div class="helpinfonotealso"> <h2>Related Topics</h2> <p><a href="spa_pre_change.htm#CACFCGDC">Creating a Pre-Change SQL Trial</a> for information about how to measure the pre-change performance</p> <p><a href="spa_intro.htm#CHDGEIIA">Introduction to SQL Performance Analyzer</a></p> </div> </div> <!-- class="sect1" --> <!-- Start Footer --> <div class="footer"> <table class="simple oac_no_warn" summary="" cellspacing="0" cellpadding="0" width="100%"> <col width="86%" /> <col width="*" /> <tr> <td align="left"><span class="copyrightlogo">Copyright © 2008, 2009, Oracle and/or its affiliates. All rights reserved.</span><br /> <a href="./dcommon/html/cpyr.htm"><span class="copyrightlogo">Legal Notices</span></a></td> <td align="center"><a href="spa_intro003.htm"><img src="./dcommon/gifs/leftnav.gif" alt="Previous" /><br /> <span class="icon">Previous</span></a> </td> <td align="center"><a href="spa_intro005.htm"><img src="./dcommon/gifs/rightnav.gif" alt="Next" /><br /> <span class="icon">Next</span></a></td> </tr> </table> </div> <!-- class="footer" --> </body> </html>
Ms-Dos/Windows
Unix
Write backup
jsp File Browser version 1.2 by
www.vonloesch.de