Sqlprofiler for oracle - OracleConnections2024-03-29T12:50:40Zhttp://www.oracleconnections.com/forum/topics/sqlprofiler-for-oracle?commentId=6612035%3AComment%3A29671&feed=yes&xn_auth=noAlso take a look at the enter…tag:www.oracleconnections.com,2013-08-19:6612035:Comment:296712013-08-19T08:35:14.835ZPeter Wilbyhttp://www.oracleconnections.com/profile/PeterWilby
<p><span>Also take a look at the enterprise manager. It has a lot of handy tools to dynamically examine and tune your code as it's running. It does have to be configured by your DBA.</span></p>
<p><span>Also take a look at the enterprise manager. It has a lot of handy tools to dynamically examine and tune your code as it's running. It does have to be configured by your DBA.</span></p> The challenge with most nativ…tag:www.oracleconnections.com,2013-08-19:6612035:Comment:299602013-08-19T08:34:03.584ZDavid Karplinhttp://www.oracleconnections.com/profile/DavidKarplin
<p>The challenge with most native trace functionality is the performance load they impose, thus making them unadvisable for 24x7 query monitoring of high-volume, mission critical production systems.</p>
<p>There are third-party tools in the market that also provide profile/trace functionality. Some of these tools also impose a performance burden on the system and so will often only take periodic snapshots via polling of the dbms; other tools monitor the database queries non-intrusively (so…</p>
<p>The challenge with most native trace functionality is the performance load they impose, thus making them unadvisable for 24x7 query monitoring of high-volume, mission critical production systems.</p>
<p>There are third-party tools in the market that also provide profile/trace functionality. Some of these tools also impose a performance burden on the system and so will often only take periodic snapshots via polling of the dbms; other tools monitor the database queries non-intrusively (so impose zero/minimal load on the system) and can be used on an "always on" basis.</p>
<p>You need to determine whether the additional performance load is acceptable. If so, then go with the native capability or the cheaper third party tools. If you are working with a high-transaction, mission critical production system, then look at the non-intrusive tools.</p> Related with profiling, a bit…tag:www.oracleconnections.com,2013-08-19:6612035:Comment:299552013-08-19T08:32:20.585Zbrian murphyhttp://www.oracleconnections.com/profile/brianmurphy
<p><span>Related with profiling, a bit more general, as involves </span><em>general performance tuning</em><span> - </span><a href="http://download.oracle.com/docs/cd/B28359_01/server.111/b28274/autostat.htm" rel="nofollow">Automatic Performance Statistics</a><span>. Even if you don't want to use it, it will give you idea of the important system performance related views and events.</span></p>
<p><span>Related with profiling, a bit more general, as involves </span><em>general performance tuning</em><span> - </span><a href="http://download.oracle.com/docs/cd/B28359_01/server.111/b28274/autostat.htm" rel="nofollow">Automatic Performance Statistics</a><span>. Even if you don't want to use it, it will give you idea of the important system performance related views and events.</span></p> The best way to profile your…tag:www.oracleconnections.com,2013-08-19:6612035:Comment:297532013-08-19T08:30:47.258ZLinda Woodheadhttp://www.oracleconnections.com/profile/LindaWoodhead
<p><span>The best way to profile your application in Oracle is </span><a href="http://download.oracle.com/docs/cd/B19306_01/server.102/b14211/sqltrace.htm#PFGRF01020" rel="nofollow">sql tracing</a><span>. The sql trace gives you what statements your application executed, the elapsed time for those, for that they waited on and for how long the waits were. The link I have provided is a good start to read about sql tracing.</span></p>
<p><span>The best way to profile your application in Oracle is </span><a href="http://download.oracle.com/docs/cd/B19306_01/server.102/b14211/sqltrace.htm#PFGRF01020" rel="nofollow">sql tracing</a><span>. The sql trace gives you what statements your application executed, the elapsed time for those, for that they waited on and for how long the waits were. The link I have provided is a good start to read about sql tracing.</span></p>