<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.technet.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>SQL and the Working Set</title><link>http://blogs.technet.com/b/askperf/archive/2007/05/18/sql-and-the-working-set.aspx</link><description>Here's an issue we've been seeing more and more of on the Performance team lately concerning SQL 2005 and Memory Management. The issue gets reported as: "Windows Memory Management is trimming the SQL Working Set." When you review the event logs, you'll</description><dc:language>en-US</dc:language><generator>Telligent Evolution Platform Developer Build (Build: 5.6.50428.7875)</generator><item><title>re: SQL and the Working Set</title><link>http://blogs.technet.com/b/askperf/archive/2007/05/18/sql-and-the-working-set.aspx#3278882</link><pubDate>Thu, 03 Sep 2009 10:09:23 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3278882</guid><dc:creator>varun dhawan</dc:creator><description>&lt;p&gt;Another gr8 post !!&lt;/p&gt;
&lt;p&gt;Couldn’t find a &amp;nbsp;better place that explain EVENT ID 17890...&lt;/p&gt;
&lt;p&gt;Thanks again!!&lt;/p&gt;
&lt;p&gt;Just one thing, elaborating the &amp;quot;BASELINE&amp;quot; and &amp;quot;FACTORS&amp;quot; could facilitate deeper understanding.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=3278882" width="1" height="1"&gt;</description></item><item><title>re: SQL and the Working Set</title><link>http://blogs.technet.com/b/askperf/archive/2007/05/18/sql-and-the-working-set.aspx#3136988</link><pubDate>Thu, 16 Oct 2008 01:18:48 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3136988</guid><dc:creator>VijayRod</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;Your above baseline calculation helped me solve a customer issue on which he even had switched hardware vendor&lt;/p&gt;
&lt;p&gt;Thank You&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=3136988" width="1" height="1"&gt;</description></item><item><title>SQL Server error: messages are appearing when the working set of SQL Server 2005 process reaches 50 percent of the memory that is committed to the process.</title><link>http://blogs.technet.com/b/askperf/archive/2007/05/18/sql-and-the-working-set.aspx#2972962</link><pubDate>Fri, 07 Mar 2008 14:19:17 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:2972962</guid><dc:creator>SQL Server Security, Performance &amp; Tuning (SSQA.net)</dc:creator><description>&lt;p&gt;Have you seen the above message within the SQL Server error logs? If not then no need to worry and make&lt;/p&gt;
&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=2972962" width="1" height="1"&gt;</description></item><item><title>Configuring Windows 2003 ( x64 ) for SQL Server</title><link>http://blogs.technet.com/b/askperf/archive/2007/05/18/sql-and-the-working-set.aspx#2717478</link><pubDate>Sun, 06 Jan 2008 23:49:19 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:2717478</guid><dc:creator>Grumpy Old DBA</dc:creator><description>&lt;p&gt;There is an almost constant stream of posts on forums asking about configuration of SQL Server 2005 memory,&lt;/p&gt;&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=2717478" width="1" height="1"&gt;</description></item><item><title>re: SQL and the Working Set</title><link>http://blogs.technet.com/b/askperf/archive/2007/05/18/sql-and-the-working-set.aspx#2036041</link><pubDate>Mon, 24 Sep 2007 22:43:24 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:2036041</guid><dc:creator>darren</dc:creator><description>&lt;p&gt;See:&lt;/p&gt;
&lt;p&gt;&lt;a rel="nofollow" target="_new" href="http://www.experts-exchange.com/Microsoft/Development/MS-SQL-Server/Q_22829413.html"&gt;http://www.experts-exchange.com/Microsoft/Development/MS-SQL-Server/Q_22829413.html&lt;/a&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=2036041" width="1" height="1"&gt;</description></item><item><title>re: SQL and the Working Set</title><link>http://blogs.technet.com/b/askperf/archive/2007/05/18/sql-and-the-working-set.aspx#1804052</link><pubDate>Wed, 22 Aug 2007 21:23:44 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:1804052</guid><dc:creator>Alexandre Grigoriev</dc:creator><description>&lt;p&gt;Regarding KB905865, won't you agree that trimming working sets behind our backs (rather than adjusting them smoothly) is a misfeature, that should have been gone when memory sizes increased beyond 256 MB. When an entry-level system has at least 512 MB, it just doesn't make sense. I get mack to my session in FUS-enabled XP, and have to wait, painfully watchilg while all my processes are being paged back in.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=1804052" width="1" height="1"&gt;</description></item><item><title>A significant part of SQL server process memory has been paged out. This may result in a performance degradation</title><link>http://blogs.technet.com/b/askperf/archive/2007/05/18/sql-and-the-working-set.aspx#1455070</link><pubDate>Fri, 06 Jul 2007 11:42:34 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:1455070</guid><dc:creator>SQL Server Security, Performance and Tuning - (SSQA)</dc:creator><description>&lt;p&gt;WIth the recent application of Service pack 2 for SQL Server we tend to see more messages on the log&lt;/p&gt;
&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=1455070" width="1" height="1"&gt;</description></item><item><title>
		   Windows Memory Management And SQL Working Set &amp;raquo; D&amp;#8217; Technology Weblog: Technology News &amp;amp; Reviews	</title><link>http://blogs.technet.com/b/askperf/archive/2007/05/18/sql-and-the-working-set.aspx#1118356</link><pubDate>Fri, 01 Jun 2007 14:19:59 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:1118356</guid><dc:creator>
		   Windows Memory Management And SQL Working Set » D’ Technology Weblog: Technology News &amp; Reviews	</dc:creator><description>&lt;p&gt;PingBack from &lt;a rel="nofollow" target="_new" href="http://www.ditii.com/blog/2007/06/01/windows-memory-management-and-sql-working-set/"&gt;http://www.ditii.com/blog/2007/06/01/windows-memory-management-and-sql-working-set/&lt;/a&gt;&lt;/p&gt;
&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=1118356" width="1" height="1"&gt;</description></item></channel></rss>