<?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; Measure CPU Pressure &#8211; CPU Business</title>
	<atom:link href="http://blog.sqlauthority.com/2009/08/17/sql-server-measure-cpu-pressure-cpu-business/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.sqlauthority.com/2009/08/17/sql-server-measure-cpu-pressure-cpu-business/</link>
	<description>Personal Notes of Pinal Dave</description>
	<lastBuildDate>Fri, 17 May 2013 15:26:57 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: SQL SERVER – Interview Questions and Answers – Frequently Asked Questions – Day 19 of 31 Journey to SQLAuthority</title>
		<link>http://blog.sqlauthority.com/2009/08/17/sql-server-measure-cpu-pressure-cpu-business/#comment-149235</link>
		<dc:creator><![CDATA[SQL SERVER – Interview Questions and Answers – Frequently Asked Questions – Day 19 of 31 Journey to SQLAuthority]]></dc:creator>
		<pubDate>Tue, 19 Jul 2011 01:30:20 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sqlauthority.com/?p=6601#comment-149235</guid>
		<description><![CDATA[[...] CPU pressure is a state wherein the CPU is fully occupied with currently assigned tasks and there are more tasks in the queue that have not yet started. (Read more here) [...]]]></description>
		<content:encoded><![CDATA[<p>[...] CPU pressure is a state wherein the CPU is fully occupied with currently assigned tasks and there are more tasks in the queue that have not yet started. (Read more here) [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Paurav</title>
		<link>http://blog.sqlauthority.com/2009/08/17/sql-server-measure-cpu-pressure-cpu-business/#comment-87349</link>
		<dc:creator><![CDATA[Paurav]]></dc:creator>
		<pubDate>Fri, 10 Sep 2010 10:26:12 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sqlauthority.com/?p=6601#comment-87349</guid>
		<description><![CDATA[Hi Pinal,

We would like to do some comparison between different processors on different servers.

Would you have any sample SQL scripts to run a stress test and provide results for comparision?

Thanks,

Paurav]]></description>
		<content:encoded><![CDATA[<p>Hi Pinal,</p>
<p>We would like to do some comparison between different processors on different servers.</p>
<p>Would you have any sample SQL scripts to run a stress test and provide results for comparision?</p>
<p>Thanks,</p>
<p>Paurav</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mandar K</title>
		<link>http://blog.sqlauthority.com/2009/08/17/sql-server-measure-cpu-pressure-cpu-business/#comment-64375</link>
		<dc:creator><![CDATA[Mandar K]]></dc:creator>
		<pubDate>Sat, 03 Apr 2010 20:47:08 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sqlauthority.com/?p=6601#comment-64375</guid>
		<description><![CDATA[Its really help fully to me....thanks pinal...]]></description>
		<content:encoded><![CDATA[<p>Its really help fully to me&#8230;.thanks pinal&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Samuel</title>
		<link>http://blog.sqlauthority.com/2009/08/17/sql-server-measure-cpu-pressure-cpu-business/#comment-59655</link>
		<dc:creator><![CDATA[Samuel]]></dc:creator>
		<pubDate>Tue, 12 Jan 2010 17:37:00 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sqlauthority.com/?p=6601#comment-59655</guid>
		<description><![CDATA[Hi Pinal, 
thru this I just want to thank you for the useful tips that you keep on giving. I am pretty new as DBA and therefore your explanations of the terms and issues are very helpful to me. Keep up the good work.
Sam]]></description>
		<content:encoded><![CDATA[<p>Hi Pinal,<br />
thru this I just want to thank you for the useful tips that you keep on giving. I am pretty new as DBA and therefore your explanations of the terms and issues are very helpful to me. Keep up the good work.<br />
Sam</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nakul Vachhrajani</title>
		<link>http://blog.sqlauthority.com/2009/08/17/sql-server-measure-cpu-pressure-cpu-business/#comment-54982</link>
		<dc:creator><![CDATA[Nakul Vachhrajani]]></dc:creator>
		<pubDate>Tue, 18 Aug 2009 17:12:07 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sqlauthority.com/?p=6601#comment-54982</guid>
		<description><![CDATA[Hello!

Thank-you for bringing to light such a nice, yet simple means of studying the &quot;CPU pressure&quot;.

Many-a-times, I have come across quite a few friends and colleagues who always say - &quot;Server performance issue? Bump-up the RAM to double the present amount&quot;. I must add here that we use a lot of virtualization for our development and RND servers, but ultimately, there is a limit and difference in the amount of juice a server can have and what is really necessary. 

Often the case is that a bad query is the root cause of your CPU spiking up for long durations of time. - which ultimately ends up frying the board. That should be the real focus of attention rather than spending thousands on hardware upgrades.

After all, if the space shuttle can still run on 8086 processors - how much computing power do we really need?

Another point where most are caught unaware is the difference between &quot;Multi-core CPU&quot; and &quot;Multi-CPU&quot; systems. While the former acts like multiple CPUs, it ultimately is probably one single physical CPU - that would reduce the number of schedulers, and lead to a bottle neck in a BI-like scenario where CPU loads are often high.

Your article is a step forward in bringing awareness about these subtle differences, and the fact that not everything has the same solution.

Looking forward to many such articles in the future.]]></description>
		<content:encoded><![CDATA[<p>Hello!</p>
<p>Thank-you for bringing to light such a nice, yet simple means of studying the &#8220;CPU pressure&#8221;.</p>
<p>Many-a-times, I have come across quite a few friends and colleagues who always say &#8211; &#8220;Server performance issue? Bump-up the RAM to double the present amount&#8221;. I must add here that we use a lot of virtualization for our development and RND servers, but ultimately, there is a limit and difference in the amount of juice a server can have and what is really necessary. </p>
<p>Often the case is that a bad query is the root cause of your CPU spiking up for long durations of time. &#8211; which ultimately ends up frying the board. That should be the real focus of attention rather than spending thousands on hardware upgrades.</p>
<p>After all, if the space shuttle can still run on 8086 processors &#8211; how much computing power do we really need?</p>
<p>Another point where most are caught unaware is the difference between &#8220;Multi-core CPU&#8221; and &#8220;Multi-CPU&#8221; systems. While the former acts like multiple CPUs, it ultimately is probably one single physical CPU &#8211; that would reduce the number of schedulers, and lead to a bottle neck in a BI-like scenario where CPU loads are often high.</p>
<p>Your article is a step forward in bringing awareness about these subtle differences, and the fact that not everything has the same solution.</p>
<p>Looking forward to many such articles in the future.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: RH</title>
		<link>http://blog.sqlauthority.com/2009/08/17/sql-server-measure-cpu-pressure-cpu-business/#comment-54975</link>
		<dc:creator><![CDATA[RH]]></dc:creator>
		<pubDate>Tue, 18 Aug 2009 14:58:43 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sqlauthority.com/?p=6601#comment-54975</guid>
		<description><![CDATA[&gt;&gt;It is quite possible that although we are running very few operations on our SQL Server, we still do not obtain the expected results.&lt;&lt;

Trivial point, but the phrase &quot;expected results&quot; has always had a pretty specific meaning for SQL Server and it is not expected performance (as in the quote) but whether the results of a query are correct.]]></description>
		<content:encoded><![CDATA[<p>&gt;&gt;It is quite possible that although we are running very few operations on our SQL Server, we still do not obtain the expected results.&lt;&lt;</p>
<p>Trivial point, but the phrase &quot;expected results&quot; has always had a pretty specific meaning for SQL Server and it is not expected performance (as in the quote) but whether the results of a query are correct.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
