<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.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>Be aware: To Hyper or not to Hyper</title><link>http://blogs.msdn.com/slavao/archive/2005/11/12/492119.aspx</link><description>Our customers observed very interesting behavior on high end Hyperthreading (HT) enabled hardware. They noticed that in some cases when high load is applied SQL Server CPU usage increases significantly but SQL Server performance degrades. Occasionally</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>re: Be aware: To Hyper or not to Hyper</title><link>http://blogs.msdn.com/slavao/archive/2005/11/12/492119.aspx#492422</link><pubDate>Mon, 14 Nov 2005 12:45:57 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:492422</guid><dc:creator>Peter Ibbotson</dc:creator><description>We've noticed this effect too. Interestingly we've also seen it on Terminal Server/Citrix machines too. Turning off HT made an unusable system suddenly usable.&lt;br&gt;I suspected the problem was something like this. What implications does this have for dual-proc machines? I'd guess very little as they don't share cache and I presume there aren't multiple system threads spawned (and I'd guess the code is a little smarter over cache coherency).</description></item><item><title>re: Be aware: To Hyper or not to Hyper</title><link>http://blogs.msdn.com/slavao/archive/2005/11/12/492119.aspx#492524</link><pubDate>Mon, 14 Nov 2005 20:12:12 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:492524</guid><dc:creator>Haidong Ji</dc:creator><description>Great information Slava. Thanks for sharing.&lt;br&gt;&lt;br&gt;I've thoroughly enjoyed your blogs so far. Keep up the great work.</description></item><item><title>re: Be aware: To Hyper or not to Hyper</title><link>http://blogs.msdn.com/slavao/archive/2005/11/12/492119.aspx#495299</link><pubDate>Mon, 21 Nov 2005 20:25:30 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:495299</guid><dc:creator>John Stephens</dc:creator><description>Can you please explain your results in more detail? &lt;br&gt;I'm not sure what I'm supposed to be looking for.</description></item><item><title>re: Be aware: To Hyper or not to Hyper</title><link>http://blogs.msdn.com/slavao/archive/2005/11/12/492119.aspx#496283</link><pubDate>Wed, 23 Nov 2005 19:19:47 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:496283</guid><dc:creator>Scotty</dc:creator><description>From your explanation I take it that multiple processors or multiple cores should not show the same problem because of the lack of shared L1 and L2 cache?</description></item><item><title>re: Be aware: To Hyper or not to Hyper</title><link>http://blogs.msdn.com/slavao/archive/2005/11/12/492119.aspx#496359</link><pubDate>Wed, 23 Nov 2005 21:05:50 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:496359</guid><dc:creator>slavao</dc:creator><description>Q1: What implications does this have for dual-proc machines?&lt;br&gt;Q2: From your explanation I take it that multiple processors or multiple cores should not show the same problem because of the lack of shared L1 and L2 cache?&lt;br&gt;A12: That is correct. Since dual procs don't share caches we shouldn't see this behavior. The same stands for cores that share neither L1 nor L2.&lt;br&gt;Q3: I'm not sure what I'm supposed to be looking for&lt;br&gt;A3: From the post: ...If the theory is correct a lock thread that shares a physical CPU with a scan thread should acquire lock much less often than other threads in a given period of time... From output above you could see whenever lock thread shares physical CPU with scan thread it acquires lock much less often as compare to other threads.</description></item><item><title>Err...</title><link>http://blogs.msdn.com/slavao/archive/2005/11/12/492119.aspx#497970</link><pubDate>Tue, 29 Nov 2005 21:27:14 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:497970</guid><dc:creator>audiofreak</dc:creator><description>Shouldn't you include Sleep(0) after SetThreadAffinityMask() before doing any work if you want to be sure that the thread runs on the core you requested?&lt;br&gt;Also, shouldn't pause instruction be inserted immediately BEFORE memory access instruction used to check the lock for it to have any effect?&lt;br&gt;</description></item><item><title>re: Be aware: To Hyper or not to Hyper</title><link>http://blogs.msdn.com/slavao/archive/2005/11/12/492119.aspx#497987</link><pubDate>Tue, 29 Nov 2005 22:19:28 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:497987</guid><dc:creator>slavao</dc:creator><description>Q1:Shouldn't you include Sleep(0) after SetThreadAffinityMask() before doing any work if you want to be sure that the thread runs on the core you requested?&lt;br&gt;A1:Nope, you don't have to. If a call to the API succeeds the thread will be bound to the CPUs described by the mask.  For more info see MSDN article &lt;a rel="nofollow" target="_new" href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dllproc/base/setthreadaffinitymask.asp"&gt;http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dllproc/base/setthreadaffinitymask.asp&lt;/a&gt;.&lt;br&gt;Q2:Also, shouldn't pause instruction be inserted immediately BEFORE memory access instruction used to check the lock for it to have any effect? &lt;br&gt;A2:No, you actually don't have to. &lt;a rel="nofollow" target="_new" href="http://www.devx.com/assets/intel/9315.pdf"&gt;http://www.devx.com/assets/intel/9315.pdf&lt;/a&gt; has a good explanation for the pause &lt;br&gt;</description></item><item><title>re: Be aware: To Hyper or not to Hyper</title><link>http://blogs.msdn.com/slavao/archive/2005/11/12/492119.aspx#499878</link><pubDate>Sun, 04 Dec 2005 18:17:29 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:499878</guid><dc:creator>guzmanda</dc:creator><description>Thanks a lot for sharing, Slava.&lt;br&gt;&lt;br&gt;I ran a controlled application test on a 4-way (8 logical) server with HT disabled/enabled at the BIOS level and observed 15-20% improvement with HT enabled. Perhaps my observation was contrary to your curtomer's experience because our app had an OLTP profile, with a ratio of about 90% read.  It may be that the lasywriter didn't have much work to do and there were few scans in my case.&lt;br&gt;&lt;br&gt;I believe this underscores your statement about the importance of application testing under load in order to understand HT implications.&lt;br&gt;</description></item><item><title>re: Be aware: To Hyper or not to Hyper</title><link>http://blogs.msdn.com/slavao/archive/2005/11/12/492119.aspx#501568</link><pubDate>Thu, 08 Dec 2005 18:33:08 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:501568</guid><dc:creator>Jon A [UK]</dc:creator><description>Just ran some testing with 6GB DB that is updated every minute 24/7 and has frequent reporting.  One of the more CPU intensive reports runs: &lt;br&gt;&lt;br&gt;with HT enabled: 13 seconds&lt;br&gt;with HT disabled (thru BIOS): 7 seconds&lt;br&gt;&lt;br&gt;Was testing with:&lt;br&gt;Dell PowerEdge 2850&lt;br&gt;W2003 Server Std &lt;br&gt;SQL2005 Std Edition&lt;br&gt;2 x XEON CPUs&lt;br&gt;4GB RAM&lt;br&gt;&lt;br&gt;I'm going to do more experimenting before deciding on disabling on our production server.</description></item><item><title>re: Be aware: To Hyper or not to Hyper</title><link>http://blogs.msdn.com/slavao/archive/2005/11/12/492119.aspx#501570</link><pubDate>Thu, 08 Dec 2005 18:33:35 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:501570</guid><dc:creator>Jon A [UK]</dc:creator><description>Just ran some testing with 6GB DB that is updated every minute 24/7 and has frequent reporting.  One of the more CPU intensive reports runs: &lt;br&gt;&lt;br&gt;with HT enabled: 13 seconds&lt;br&gt;with HT disabled (thru BIOS): 7 seconds&lt;br&gt;&lt;br&gt;Was testing with:&lt;br&gt;Dell PowerEdge 2850&lt;br&gt;W2003 Server Std &lt;br&gt;SQL2005 Std Edition&lt;br&gt;2 x XEON CPUs&lt;br&gt;4GB RAM&lt;br&gt;&lt;br&gt;I'm going to do more experimenting before deciding on disabling on our production server.</description></item><item><title>re: Be aware: To Hyper or not to Hyper</title><link>http://blogs.msdn.com/slavao/archive/2005/11/12/492119.aspx#502707</link><pubDate>Mon, 12 Dec 2005 17:09:01 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:502707</guid><dc:creator>Jerry Foster</dc:creator><description>When we switched to 2000 sp4, our system became almost unusable at times.  We noticed a drastic increase in CPU usage but performance just tanked, especially under load. I wish Slava could run his test after upgrading to sp4 to see if it gets worse.&lt;br&gt;&lt;br&gt;We've considered disabling HT, but are afraid to risk making our current problems even worse.&lt;br&gt;&lt;br&gt;We do have before/after test environments, but unfortunately we simply cannot recreate the necessary load level from our production box to accurately test.</description></item><item><title>re: Be aware: To Hyper or not to Hyper</title><link>http://blogs.msdn.com/slavao/archive/2005/11/12/492119.aspx#506349</link><pubDate>Wed, 21 Dec 2005 18:40:11 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:506349</guid><dc:creator>Rosa</dc:creator><description>Does setting the &amp;quot;max degree of parallelism&amp;quot; in SQL Server to the number of physical processors have the same effect as disabling HT?  Or is it better to disable HT?</description></item><item><title>re: Be aware: To Hyper or not to Hyper</title><link>http://blogs.msdn.com/slavao/archive/2005/11/12/492119.aspx#509154</link><pubDate>Wed, 04 Jan 2006 15:49:28 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:509154</guid><dc:creator>jrobertobr</dc:creator><description>   I think reducing max degree of parallelism could cause a query to run only on the logical processors, because all processors are still avaliable to SQL.&lt;br&gt;   I guess disabling the use of logical processors by SQL server (Processor Control under SQL Server Properties), not disbling HTT on BIOS should give the same performance improvements on SQL server, leaving the OS with all the processors.&lt;br&gt;   Again, it's all a case-by-case situation, that must be tested before any action to be taken.</description></item><item><title>HyperThreading and SQL</title><link>http://blogs.msdn.com/slavao/archive/2005/11/12/492119.aspx#536357</link><pubDate>Wed, 22 Feb 2006 00:30:38 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:536357</guid><dc:creator>Watson's Ramblings</dc:creator><description /></item><item><title>re: Be aware: To Hyper or not to Hyper</title><link>http://blogs.msdn.com/slavao/archive/2005/11/12/492119.aspx#574982</link><pubDate>Wed, 12 Apr 2006 18:12:28 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:574982</guid><dc:creator>Rusty</dc:creator><description>A well presented article. As a matter of precaution on my SQL servers I disabled HP by default.</description></item><item><title>Lessons learned from upgrading to SQL Server 2005 and upgrading the hardware</title><link>http://blogs.msdn.com/slavao/archive/2005/11/12/492119.aspx#586349</link><pubDate>Sat, 29 Apr 2006 00:05:10 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:586349</guid><dc:creator>Real Life Microsoft IT</dc:creator><description>We recently upgraded from SQL Server 2005 (from SQL Server 2000) and also simultaneously the hardware...</description></item><item><title>Hyper-Threading and Shared CPU Cache</title><link>http://blogs.msdn.com/slavao/archive/2005/11/12/492119.aspx#664739</link><pubDate>Thu, 13 Jul 2006 21:15:21 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:664739</guid><dc:creator>Craig Stuntz's Weblog</dc:creator><description /></item><item><title>ADO.NET and asynchronous commands</title><link>http://blogs.msdn.com/slavao/archive/2005/11/12/492119.aspx#735435</link><pubDate>Fri, 01 Sep 2006 18:42:19 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:735435</guid><dc:creator>Watson's Ramblings</dc:creator><description /></item><item><title>Maximum Degree of Parallelism and Hyperthreading </title><link>http://blogs.msdn.com/slavao/archive/2005/11/12/492119.aspx#1069265</link><pubDate>Mon, 13 Nov 2006 19:17:01 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:1069265</guid><dc:creator>Lara's Blog</dc:creator><description>&lt;p&gt;For those who are challenged with deciphering how to configure the max degree of parallelism on a server...&lt;/p&gt;
</description></item><item><title>Maximum Degree of Parallelism and Hyperthreading </title><link>http://blogs.msdn.com/slavao/archive/2005/11/12/492119.aspx#1101924</link><pubDate>Sun, 19 Nov 2006 07:38:16 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:1101924</guid><dc:creator>Lara's Blog</dc:creator><description>&lt;p&gt;For those who are challenged with deciphering how to configure the max degree of parallelism on a server&lt;/p&gt;
</description></item><item><title>re: Be aware: To Hyper or not to Hyper</title><link>http://blogs.msdn.com/slavao/archive/2005/11/12/492119.aspx#1232813</link><pubDate>Thu, 07 Dec 2006 17:11:06 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:1232813</guid><dc:creator>Glen Sidelnikov</dc:creator><description>&lt;p&gt;Would this explain an actual performance degradation we are currently seeing on our production box? We are using x64 8 XEON CPU with 16 GB or RAM with WIndows 2003 R2 Enterprise and SQL 2005 64 bit Enterprise. &amp;quot;Production&amp;quot; box is still in testing mode. There is no heavy load. Sproc batch that is running 15 seconds on the &amp;quot;test&amp;quot; box (Two Zeon CPU x86 with 4 GB of RAM running Windows 2003 32 bit + SQL 2005 Standard) is running 24 seconds on production.&lt;/p&gt;
&lt;p&gt;Thank you. &lt;/p&gt;</description></item><item><title>re: Be aware: To Hyper or not to Hyper</title><link>http://blogs.msdn.com/slavao/archive/2005/11/12/492119.aspx#1400977</link><pubDate>Wed, 03 Jan 2007 02:44:15 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:1400977</guid><dc:creator>slavao</dc:creator><description>&lt;p&gt;Most likely not. In order to find the real culprit you will need to do perf analysis &lt;/p&gt;
&lt;p&gt;1. Make hardware sanity check: Disks, CPUs cache sizes, and etc... For example It is better for 64bit systems have larger CPU caches. &lt;/p&gt;
&lt;p&gt;2. Check query plan&lt;/p&gt;
&lt;p&gt;3. Check perfmon counters and find possible discrepancies that will explain the degradation. &lt;/p&gt;
</description></item><item><title>   [Performance] Hyper-threading and .NET &amp;raquo; Advanced .NET Debugging</title><link>http://blogs.msdn.com/slavao/archive/2005/11/12/492119.aspx#1454465</link><pubDate>Fri, 12 Jan 2007 11:49:23 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:1454465</guid><dc:creator>   [Performance] Hyper-threading and .NET » Advanced .NET Debugging</dc:creator><description>&lt;p&gt;PingBack from &lt;a rel="nofollow" target="_new" href="http://dotnetdebug.net/2005/11/20/performance-hyper-threading-and-net/"&gt;http://dotnetdebug.net/2005/11/20/performance-hyper-threading-and-net/&lt;/a&gt;&lt;/p&gt;
</description></item><item><title>Yedda: RE: Is Hyperthreading Still being used in new processors?</title><link>http://blogs.msdn.com/slavao/archive/2005/11/12/492119.aspx#2652857</link><pubDate>Tue, 15 May 2007 20:15:12 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:2652857</guid><dc:creator>MrViklund's answers on Yedda - People. Sharing. Knowledge.</dc:creator><description>&lt;p&gt;MrViklund answered: re:After Intel launched the new dual core processors, is Hyperthreading still relevant? Is it still being used in new Intel processors?&lt;/p&gt;
</description></item><item><title>The Perils of Hyperthreading for SQL Server</title><link>http://blogs.msdn.com/slavao/archive/2005/11/12/492119.aspx#4475587</link><pubDate>Mon, 20 Aug 2007 11:02:51 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:4475587</guid><dc:creator>Kevin Kline</dc:creator><description>&lt;p&gt;Just a quick note to send a big Thank You to Christoph Stotz of Frankfurt, Germany for his hospitality&lt;/p&gt;
</description></item><item><title>DBS Works  &amp;raquo; Blog Archive   &amp;raquo; Programming references</title><link>http://blogs.msdn.com/slavao/archive/2005/11/12/492119.aspx#5526076</link><pubDate>Fri, 19 Oct 2007 19:54:03 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:5526076</guid><dc:creator>DBS Works  » Blog Archive   » Programming references</dc:creator><description>&lt;p&gt;PingBack from &lt;a rel="nofollow" target="_new" href="http://dbsworks.com/?p=8"&gt;http://dbsworks.com/?p=8&lt;/a&gt;&lt;/p&gt;
</description></item><item><title>Προβληματισμός: To Hyper or not to Hyper</title><link>http://blogs.msdn.com/slavao/archive/2005/11/12/492119.aspx#7595010</link><pubDate>Mon, 11 Feb 2008 02:36:59 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:7595010</guid><dc:creator>Καθημερινή Ρουτίνα</dc:creator><description>&lt;p&gt;Ο προβληματισμός γεννήθηκε στην μέση της εγκατάστασης μιας εφαρμογής που έκανε χρήση των Analysis Services&lt;/p&gt;
</description></item><item><title>Welcome -- Ax Database Configuration Checklist part 1</title><link>http://blogs.msdn.com/slavao/archive/2005/11/12/492119.aspx#8172527</link><pubDate>Wed, 12 Mar 2008 21:54:15 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8172527</guid><dc:creator>Dynamics Ax Performance team</dc:creator><description>&lt;p&gt;Welcome to the Dynamics Ax Performance Team's blog. We're putting together a team introduction and hope&lt;/p&gt;
</description></item><item><title>Ax Database Configuration Checklist part 1 &amp;laquo; Cool hakE</title><link>http://blogs.msdn.com/slavao/archive/2005/11/12/492119.aspx#8768182</link><pubDate>Thu, 24 Jul 2008 03:35:32 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8768182</guid><dc:creator>Ax Database Configuration Checklist part 1 &amp;laquo; Cool hakE</dc:creator><description>&lt;p&gt;PingBack from &lt;a rel="nofollow" target="_new" href="http://coolhake.wordpress.com/2008/07/24/ax-database-configuration-checklist-part-1/"&gt;http://coolhake.wordpress.com/2008/07/24/ax-database-configuration-checklist-part-1/&lt;/a&gt;&lt;/p&gt;
</description></item><item><title>Hyper threading e degrado delle prestazioni | hilpers</title><link>http://blogs.msdn.com/slavao/archive/2005/11/12/492119.aspx#9356722</link><pubDate>Wed, 21 Jan 2009 19:22:14 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9356722</guid><dc:creator>Hyper threading e degrado delle prestazioni | hilpers</dc:creator><description>&lt;p&gt;PingBack from &lt;a rel="nofollow" target="_new" href="http://www.hilpers.it/2532841-hyper-threading-e-degrado-delle"&gt;http://www.hilpers.it/2532841-hyper-threading-e-degrado-delle&lt;/a&gt;&lt;/p&gt;
</description></item><item><title>100% du CPU avec base de donn?es. - Page 5 | hilpers</title><link>http://blogs.msdn.com/slavao/archive/2005/11/12/492119.aspx#9368488</link><pubDate>Thu, 22 Jan 2009 18:36:37 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9368488</guid><dc:creator>100% du CPU avec base de donn?es. - Page 5 | hilpers</dc:creator><description>&lt;p&gt;PingBack from &lt;a rel="nofollow" target="_new" href="http://www.hilpers.fr/918559-100-du-cpu-avec-base/5"&gt;http://www.hilpers.fr/918559-100-du-cpu-avec-base/5&lt;/a&gt;&lt;/p&gt;
</description></item><item><title> Slava Oks s WebLog Be aware To Hyper or not to Hyper | Wood TV Stand</title><link>http://blogs.msdn.com/slavao/archive/2005/11/12/492119.aspx#9678916</link><pubDate>Mon, 01 Jun 2009 20:40:36 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9678916</guid><dc:creator> Slava Oks s WebLog Be aware To Hyper or not to Hyper | Wood TV Stand</dc:creator><description>&lt;p&gt;PingBack from &lt;a rel="nofollow" target="_new" href="http://woodtvstand.info/story.php?id=11938"&gt;http://woodtvstand.info/story.php?id=11938&lt;/a&gt;&lt;/p&gt;
</description></item><item><title> Slava Oks s WebLog Be aware To Hyper or not to Hyper | Paid Surveys</title><link>http://blogs.msdn.com/slavao/archive/2005/11/12/492119.aspx#9684040</link><pubDate>Tue, 02 Jun 2009 10:06:36 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9684040</guid><dc:creator> Slava Oks s WebLog Be aware To Hyper or not to Hyper | Paid Surveys</dc:creator><description>&lt;p&gt;PingBack from &lt;a rel="nofollow" target="_new" href="http://paidsurveyshub.info/story.php?id=76073"&gt;http://paidsurveyshub.info/story.php?id=76073&lt;/a&gt;&lt;/p&gt;
</description></item><item><title> Slava Oks s WebLog Be aware To Hyper or not to Hyper | Insomnia Cure</title><link>http://blogs.msdn.com/slavao/archive/2005/11/12/492119.aspx#9720062</link><pubDate>Wed, 10 Jun 2009 04:04:54 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9720062</guid><dc:creator> Slava Oks s WebLog Be aware To Hyper or not to Hyper | Insomnia Cure</dc:creator><description>&lt;p&gt;PingBack from &lt;a rel="nofollow" target="_new" href="http://insomniacuresite.info/story.php?id=1820"&gt;http://insomniacuresite.info/story.php?id=1820&lt;/a&gt;&lt;/p&gt;
</description></item><item><title>Ax Database Configuration Checklist Part 1</title><link>http://blogs.msdn.com/slavao/archive/2005/11/12/492119.aspx#9763111</link><pubDate>Tue, 16 Jun 2009 23:58:44 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9763111</guid><dc:creator>Pin Wang's AX Blog</dc:creator><description>&lt;p&gt;Assumptions : Dedicated SQL Server 2005 Server (does not run any other major applications besides SQL&lt;/p&gt;
</description></item></channel></rss>