<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Identifying SQL Execution Bottlenecks Scientifically</title>
	<atom:link href="http://www.pythian.com/news/937/identifying-sql-execution-bottlenecks-scientifically/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.pythian.com/news/937/identifying-sql-execution-bottlenecks-scientifically/</link>
	<description>News and views from Pythian DBAs</description>
	<lastBuildDate>Fri, 10 Feb 2012 13:01:25 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.4</generator>
	<item>
		<title>By: Yong Huang</title>
		<link>http://www.pythian.com/news/937/identifying-sql-execution-bottlenecks-scientifically/#comment-333885</link>
		<dc:creator>Yong Huang</dc:creator>
		<pubDate>Tue, 27 Jan 2009 20:38:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.pythian.com/blogs/937/identifying-sql-execution-bottlenecks-scientifically#comment-333885</guid>
		<description>Also, although &quot;It is not possible to turn on the statistics_level parameter on an already-executing session&quot;, you can turn on _rowsource_execution_statistics for an existing session:

exec dbms_system.set_bool_param_in_session(, , &#039;_rowsource_execution_statistics&#039;, true)

For others (not you!) that don&#039;t know, that parameter, controlled by statistics_level, is the one that precisely turns on the row level stats shown in the plan.

Poeple have been wishing for years to have a procedure like set_string_param_in_session in dbms_system. Dream has not come true!</description>
		<content:encoded><![CDATA[<p>Also, although &#8220;It is not possible to turn on the statistics_level parameter on an already-executing session&#8221;, you can turn on _rowsource_execution_statistics for an existing session:</p>
<p>exec dbms_system.set_bool_param_in_session(, , &#8216;_rowsource_execution_statistics&#8217;, true)</p>
<p>For others (not you!) that don&#8217;t know, that parameter, controlled by statistics_level, is the one that precisely turns on the row level stats shown in the plan.</p>
<p>Poeple have been wishing for years to have a procedure like set_string_param_in_session in dbms_system. Dream has not come true!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Yong Huang</title>
		<link>http://www.pythian.com/news/937/identifying-sql-execution-bottlenecks-scientifically/#comment-333883</link>
		<dc:creator>Yong Huang</dc:creator>
		<pubDate>Tue, 27 Jan 2009 20:31:27 +0000</pubDate>
		<guid isPermaLink="false">http://www.pythian.com/blogs/937/identifying-sql-execution-bottlenecks-scientifically#comment-333883</guid>
		<description>Riyaj,

Great article!

You have a typo in gather table stats. t2_vc was gathered twice; the first one should be for t1_vc. Also, after you create index t1_vc_i2 on t1_vc (n2,n1), why do you re-gather stats for table t1_vc? Index stats is automatically created (unless you turn off _optimizer_compute_index_stats), table stats stay the same anyway.</description>
		<content:encoded><![CDATA[<p>Riyaj,</p>
<p>Great article!</p>
<p>You have a typo in gather table stats. t2_vc was gathered twice; the first one should be for t1_vc. Also, after you create index t1_vc_i2 on t1_vc (n2,n1), why do you re-gather stats for table t1_vc? Index stats is automatically created (unless you turn off _optimizer_compute_index_stats), table stats stay the same anyway.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

