<?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; Guest Post &#8211; Jonathan Kehayias &#8211; Wait Type &#8211; Day 16 of 28</title>
	<atom:link href="http://blog.sqlauthority.com/2011/02/16/sql-server-guest-post-jonathan-kehayias-wait-type-day-16-of-28/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.sqlauthority.com/2011/02/16/sql-server-guest-post-jonathan-kehayias-wait-type-day-16-of-28/</link>
	<description>SQL, SQL Server, MySQL, Big Data and NoSQL</description>
	<lastBuildDate>Wed, 19 Jun 2013 08:01:41 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: SQL SERVER &#8211; Weekly Series &#8211; Memory Lane &#8211; #016 &#171; SQL Server Journey with SQL Authority</title>
		<link>http://blog.sqlauthority.com/2011/02/16/sql-server-guest-post-jonathan-kehayias-wait-type-day-16-of-28/#comment-422310</link>
		<dc:creator><![CDATA[SQL SERVER &#8211; Weekly Series &#8211; Memory Lane &#8211; #016 &#171; SQL Server Journey with SQL Authority]]></dc:creator>
		<pubDate>Sat, 16 Feb 2013 01:31:57 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sqlauthority.com/?p=12015#comment-422310</guid>
		<description><![CDATA[[...] Guest Post – Jonathan Kehayias – Wait Type – Day 16 of 28 [...]]]></description>
		<content:encoded><![CDATA[<p>[...] Guest Post – Jonathan Kehayias – Wait Type – Day 16 of 28 [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Doug- Sarasota</title>
		<link>http://blog.sqlauthority.com/2011/02/16/sql-server-guest-post-jonathan-kehayias-wait-type-day-16-of-28/#comment-118831</link>
		<dc:creator><![CDATA[Doug- Sarasota]]></dc:creator>
		<pubDate>Wed, 16 Feb 2011 14:48:52 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sqlauthority.com/?p=12015#comment-118831</guid>
		<description><![CDATA[Jonathan&#039;s blog is a must-read and his sessions at events like sqlpass are fantastic.  Thanks Jonathan!

(Go Gators)]]></description>
		<content:encoded><![CDATA[<p>Jonathan&#8217;s blog is a must-read and his sessions at events like sqlpass are fantastic.  Thanks Jonathan!</p>
<p>(Go Gators)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jonathan Kehayias</title>
		<link>http://blog.sqlauthority.com/2011/02/16/sql-server-guest-post-jonathan-kehayias-wait-type-day-16-of-28/#comment-118754</link>
		<dc:creator><![CDATA[Jonathan Kehayias]]></dc:creator>
		<pubDate>Wed, 16 Feb 2011 01:53:25 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sqlauthority.com/?p=12015#comment-118754</guid>
		<description><![CDATA[A quick note upon re-reading this for the xteenth time that I should point out.  First, the numbers used as examples for &#039;max server memory&#039; with 16GB and 32GB RAM should not be considered to be best practice numbers, I pulled them out of the air for the purposes of this post because they provided easier numbers to work with.  Tuning the &#039;max server memory&#039; sp_configure option should be done based on the requirements of each specific server, through consistent monitoring of the Memory\Available MBytes performance counter, which should remain above 150 at all times.]]></description>
		<content:encoded><![CDATA[<p>A quick note upon re-reading this for the xteenth time that I should point out.  First, the numbers used as examples for &#8216;max server memory&#8217; with 16GB and 32GB RAM should not be considered to be best practice numbers, I pulled them out of the air for the purposes of this post because they provided easier numbers to work with.  Tuning the &#8216;max server memory&#8217; sp_configure option should be done based on the requirements of each specific server, through consistent monitoring of the Memory\Available MBytes performance counter, which should remain above 150 at all times.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
