<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://www2.sqlblog.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Adam Machanic : memory</title><link>http://www2.sqlblog.com/blogs/adam_machanic/archive/tags/memory/default.aspx</link><description>Tags: memory</description><dc:language>en</dc:language><generator>CommunityServer 2.1 SP2 (Build: 61129.1)</generator><item><title>PASS Summit 2011 - Zen and the Art of Workspace Memory - Demos</title><link>http://www2.sqlblog.com/blogs/adam_machanic/archive/2011/10/16/pass-summit-2011-zen-and-the-art-of-workspace-memory-demos.aspx</link><pubDate>Mon, 17 Oct 2011 00:23:00 GMT</pubDate><guid isPermaLink="false">21093a07-8b3d-42db-8cbf-3350fcbf5496:39085</guid><dc:creator>Adam Machanic</dc:creator><slash:comments>18</slash:comments><comments>http://www2.sqlblog.com/blogs/adam_machanic/comments/39085.aspx</comments><wfw:commentRss>http://www2.sqlblog.com/blogs/adam_machanic/commentrss.aspx?PostID=39085</wfw:commentRss><description>What a rush . Standing on the stage in an almost-full 1,000-person room, I (very) momentarily wondered what I'd been thinking when I submitted a 500-level talk for the biggest SQL Server conference in the world. But despite a rough start--my laptop crashed...(&lt;a href="http://www2.sqlblog.com/blogs/adam_machanic/archive/2011/10/16/pass-summit-2011-zen-and-the-art-of-workspace-memory-demos.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://www2.sqlblog.com/aggbug.aspx?PostID=39085" width="1" height="1"&gt;</description><enclosure url="http://www2.sqlblog.com/blogs/adam_machanic/attachment/39085.ashx" length="66600" type="application/x-zip-compressed" /><category domain="http://www2.sqlblog.com/blogs/adam_machanic/archive/tags/memory/default.aspx">memory</category><category domain="http://www2.sqlblog.com/blogs/adam_machanic/archive/tags/Optimization/default.aspx">Optimization</category><category domain="http://www2.sqlblog.com/blogs/adam_machanic/archive/tags/PASS/default.aspx">PASS</category><category domain="http://www2.sqlblog.com/blogs/adam_machanic/archive/tags/Performance/default.aspx">Performance</category><category domain="http://www2.sqlblog.com/blogs/adam_machanic/archive/tags/Query+Tuning/default.aspx">Query Tuning</category></item><item><title>SQL Server Procedure Cache: More Relief on the Way</title><link>http://www2.sqlblog.com/blogs/adam_machanic/archive/2008/04/15/sql-server-procedure-cache-more-relief-on-the-way.aspx</link><pubDate>Wed, 16 Apr 2008 00:26:00 GMT</pubDate><guid isPermaLink="false">21093a07-8b3d-42db-8cbf-3350fcbf5496:6234</guid><dc:creator>Adam Machanic</dc:creator><slash:comments>3</slash:comments><comments>http://www2.sqlblog.com/blogs/adam_machanic/comments/6234.aspx</comments><wfw:commentRss>http://www2.sqlblog.com/blogs/adam_machanic/commentrss.aspx?PostID=6234</wfw:commentRss><description>&lt;p&gt;If you've read many of my blog posts, you know 
that I consider lack of procedure cache control to be a &lt;a href="http://sqlblog.com/blogs/adam_machanic/archive/2007/08/14/want-to-control-the-procedure-cache.aspx" class=""&gt;major SQL Server pain point&lt;/a&gt;. Badly written apps 
that use non-parameterized ad hoc queries can quickly flood SQL Server's memory 
pools and bring the server to its knees. &lt;/p&gt;
&lt;p&gt;SQL Server 2005 brought some relief in the form of 
the Forced Parameterization database option, and SP2 took things one step 
further with better throttling of the cache... but it's still not&amp;nbsp;enough.&amp;nbsp;We 
want a knob!&lt;/p&gt;
&lt;p&gt;The bad news: We're not getting quite the knob I 
was hoping for.&lt;/p&gt;
&lt;p&gt;The good news: SQL Server 2008 will include an 
&lt;strong&gt;sp_configure&lt;/strong&gt; option called&amp;nbsp;"&lt;strong&gt;optimize for ad hoc workloads&lt;/strong&gt;".&amp;nbsp; This option 
will cause the procedure cache to only cache the parameterized stubs for ad hoc 
queries, rather than the full query with parameters.&amp;nbsp; This means that 
applications passing a large number of non-parameterized batches should see much 
lower procedure cache memory utilization and, therefore, better overall 
throughput.&amp;nbsp; I'm really looking forward to seeing this in action;&amp;nbsp;this feature 
should be added with&amp;nbsp;the next&amp;nbsp;pre-release drop.&lt;/p&gt;
&lt;p&gt;Remember, there is simply no substitute for 
properly designing your application's data access layer, but hopefully this will 
help for those applications that simply can't be changed...&lt;/p&gt;&lt;img src="http://www2.sqlblog.com/aggbug.aspx?PostID=6234" width="1" height="1"&gt;</description><category domain="http://www2.sqlblog.com/blogs/adam_machanic/archive/tags/memory/default.aspx">memory</category><category domain="http://www2.sqlblog.com/blogs/adam_machanic/archive/tags/Performance/default.aspx">Performance</category><category domain="http://www2.sqlblog.com/blogs/adam_machanic/archive/tags/procedure+cache/default.aspx">procedure cache</category></item></channel></rss>