<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: SQL SERVER &#8211; 2005 &#8211; Forced Parameterization and Simple Parameterization &#8211; T-SQL and SSMS</title>
	<atom:link href="http://blog.sqlauthority.com/2007/10/25/sql-server-2005-forced-parameterization-and-simple-parameterization-t-sql-and-ssms/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.sqlauthority.com/2007/10/25/sql-server-2005-forced-parameterization-and-simple-parameterization-t-sql-and-ssms/</link>
	<description>Personal Notes of Pinal Dave</description>
	<lastBuildDate>Mon, 13 Feb 2012 15:11:24 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Abhay</title>
		<link>http://blog.sqlauthority.com/2007/10/25/sql-server-2005-forced-parameterization-and-simple-parameterization-t-sql-and-ssms/#comment-168382</link>
		<dc:creator><![CDATA[Abhay]]></dc:creator>
		<pubDate>Thu, 15 Sep 2011 13:45:15 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sqlauthority.com/2007/10/25/sql-server-2005-forced-parameterization-and-simple-parameterization-t-sql-and-ssms/#comment-168382</guid>
		<description><![CDATA[If you set this option to on all the plans will flush becasue of this setting .It is next time that the new plans will be used .After that , yes there is a probability that for a long time the same plan is used which might not be the best in future until its in the cache as per page life expectancy..]]></description>
		<content:encoded><![CDATA[<p>If you set this option to on all the plans will flush becasue of this setting .It is next time that the new plans will be used .After that , yes there is a probability that for a long time the same plan is used which might not be the best in future until its in the cache as per page life expectancy..</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: vishal ghawate</title>
		<link>http://blog.sqlauthority.com/2007/10/25/sql-server-2005-forced-parameterization-and-simple-parameterization-t-sql-and-ssms/#comment-117180</link>
		<dc:creator><![CDATA[vishal ghawate]]></dc:creator>
		<pubDate>Tue, 08 Feb 2011 05:04:18 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sqlauthority.com/2007/10/25/sql-server-2005-forced-parameterization-and-simple-parameterization-t-sql-and-ssms/#comment-117180</guid>
		<description><![CDATA[in forced parameterazation how select ,update, delete how converted to parameters?]]></description>
		<content:encoded><![CDATA[<p>in forced parameterazation how select ,update, delete how converted to parameters?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stephen</title>
		<link>http://blog.sqlauthority.com/2007/10/25/sql-server-2005-forced-parameterization-and-simple-parameterization-t-sql-and-ssms/#comment-95780</link>
		<dc:creator><![CDATA[Stephen]]></dc:creator>
		<pubDate>Mon, 25 Oct 2010 22:42:01 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sqlauthority.com/2007/10/25/sql-server-2005-forced-parameterization-and-simple-parameterization-t-sql-and-ssms/#comment-95780</guid>
		<description><![CDATA[Amel - No, don&#039;t apply (OPTION RECOMPILE). The TechNet article at http://technet.microsoft.com/en-us/library/ms175037.aspx states quite clearly that queries with a RECOMPILE hint are not eligible for forced parameterisation.

I guess you&#039;re trying to get the best &#039;first reusable plan&#039; to be created once the forced parameterisation kicks in.  If so, relax.  That same TechNet article says that &quot;...Setting the PARAMETERIZATION option to FORCED flushes all query plans from the plan cache of a database...&quot;]]></description>
		<content:encoded><![CDATA[<p>Amel &#8211; No, don&#8217;t apply (OPTION RECOMPILE). The TechNet article at <a href="http://technet.microsoft.com/en-us/library/ms175037.aspx" rel="nofollow">http://technet.microsoft.com/en-us/library/ms175037.aspx</a> states quite clearly that queries with a RECOMPILE hint are not eligible for forced parameterisation.</p>
<p>I guess you&#8217;re trying to get the best &#8216;first reusable plan&#8217; to be created once the forced parameterisation kicks in.  If so, relax.  That same TechNet article says that &#8220;&#8230;Setting the PARAMETERIZATION option to FORCED flushes all query plans from the plan cache of a database&#8230;&#8221;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Amel Musić</title>
		<link>http://blog.sqlauthority.com/2007/10/25/sql-server-2005-forced-parameterization-and-simple-parameterization-t-sql-and-ssms/#comment-56750</link>
		<dc:creator><![CDATA[Amel Musić]]></dc:creator>
		<pubDate>Fri, 16 Oct 2009 11:03:19 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sqlauthority.com/2007/10/25/sql-server-2005-forced-parameterization-and-simple-parameterization-t-sql-and-ssms/#comment-56750</guid>
		<description><![CDATA[When setting parametrization to FORCED, good thing is to put on every query (OPTION RECOMPILE) because, if we stored first query plan that is not optimal, every other request will use this bad plan, and we can get bad performance :)]]></description>
		<content:encoded><![CDATA[<p>When setting parametrization to FORCED, good thing is to put on every query (OPTION RECOMPILE) because, if we stored first query plan that is not optimal, every other request will use this bad plan, and we can get bad performance :)</p>
]]></content:encoded>
	</item>
</channel>
</rss>

