<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://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>Linchi Shea : Performance</title><link>http://sqlblog.com/blogs/linchi_shea/archive/tags/Performance/default.aspx</link><description>Tags: Performance</description><dc:language>en</dc:language><generator>CommunityServer 2.1 SP2 (Build: 61129.1)</generator><item><title>Performance impact: the cost of NUMA remote memory access</title><link>http://sqlblog.com/blogs/linchi_shea/archive/2012/01/30/performance-impact-the-cost-of-numa-remote-memory-access.aspx</link><pubDate>Mon, 30 Jan 2012 23:17:20 GMT</pubDate><guid isPermaLink="false">21093a07-8b3d-42db-8cbf-3350fcbf5496:41450</guid><dc:creator>Linchi Shea</dc:creator><slash:comments>10</slash:comments><comments>http://sqlblog.com/blogs/linchi_shea/comments/41450.aspx</comments><wfw:commentRss>http://sqlblog.com/blogs/linchi_shea/commentrss.aspx?PostID=41450</wfw:commentRss><description>These days if you get a new server-class machine to run SQL Server, you can almost be 100% sure that it’ll be running on NUMA hardware. The recent AMD Opteron and Intel Nehalem-based processors are all built on some form of NUMA architecture. The current...(&lt;a href="http://sqlblog.com/blogs/linchi_shea/archive/2012/01/30/performance-impact-the-cost-of-numa-remote-memory-access.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://sqlblog.com/aggbug.aspx?PostID=41450" width="1" height="1"&gt;</description><category domain="http://sqlblog.com/blogs/linchi_shea/archive/tags/Performance/default.aspx">Performance</category><category domain="http://sqlblog.com/blogs/linchi_shea/archive/tags/Benchmark/default.aspx">Benchmark</category><category domain="http://sqlblog.com/blogs/linchi_shea/archive/tags/Memory+speed/default.aspx">Memory speed</category><category domain="http://sqlblog.com/blogs/linchi_shea/archive/tags/NUMA/default.aspx">NUMA</category><category domain="http://sqlblog.com/blogs/linchi_shea/archive/tags/NUMA+affinity/default.aspx">NUMA affinity</category><category domain="http://sqlblog.com/blogs/linchi_shea/archive/tags/Remote+memory+access/default.aspx">Remote memory access</category><category domain="http://sqlblog.com/blogs/linchi_shea/archive/tags/Local+memory+access/default.aspx">Local memory access</category></item><item><title>Performance impact: hyperthreading for OLTP queries -- II</title><link>http://sqlblog.com/blogs/linchi_shea/archive/2012/01/11/performance-impact-hyperthreading-for-oltp-queries-ii.aspx</link><pubDate>Wed, 11 Jan 2012 18:51:17 GMT</pubDate><guid isPermaLink="false">21093a07-8b3d-42db-8cbf-3350fcbf5496:40959</guid><dc:creator>Linchi Shea</dc:creator><slash:comments>8</slash:comments><comments>http://sqlblog.com/blogs/linchi_shea/comments/40959.aspx</comments><wfw:commentRss>http://sqlblog.com/blogs/linchi_shea/commentrss.aspx?PostID=40959</wfw:commentRss><description>This is in part a response to a comment by Paul White ( @SQL_Kiwi ) to my previous post on the performance impact of enabling hyperthreading (HT) on OLTP queries , and in part due to my desire to capture a more complete set of test data for future investigation...(&lt;a href="http://sqlblog.com/blogs/linchi_shea/archive/2012/01/11/performance-impact-hyperthreading-for-oltp-queries-ii.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://sqlblog.com/aggbug.aspx?PostID=40959" width="1" height="1"&gt;</description><category domain="http://sqlblog.com/blogs/linchi_shea/archive/tags/Performance/default.aspx">Performance</category><category domain="http://sqlblog.com/blogs/linchi_shea/archive/tags/Testing/default.aspx">Testing</category><category domain="http://sqlblog.com/blogs/linchi_shea/archive/tags/Query+Processing/default.aspx">Query Processing</category><category domain="http://sqlblog.com/blogs/linchi_shea/archive/tags/Benchmark/default.aspx">Benchmark</category><category domain="http://sqlblog.com/blogs/linchi_shea/archive/tags/hyperthreading/default.aspx">hyperthreading</category></item><item><title>Performance impact: hyperthreading for OLTP queries</title><link>http://sqlblog.com/blogs/linchi_shea/archive/2012/01/06/performance-impact-hyperthreading-for-oltp-queries.aspx</link><pubDate>Fri, 06 Jan 2012 04:44:00 GMT</pubDate><guid isPermaLink="false">21093a07-8b3d-42db-8cbf-3350fcbf5496:40853</guid><dc:creator>Linchi Shea</dc:creator><slash:comments>24</slash:comments><comments>http://sqlblog.com/blogs/linchi_shea/comments/40853.aspx</comments><wfw:commentRss>http://sqlblog.com/blogs/linchi_shea/commentrss.aspx?PostID=40853</wfw:commentRss><description>My previous post focuses on the performance impact of enabling hyperthreading (HT) on a machine with four Intel Westmere-EX processors on reporting queries. Let’s turn our attention to OLTP queries. To oversimplify it, reporting queries are generally...(&lt;a href="http://sqlblog.com/blogs/linchi_shea/archive/2012/01/06/performance-impact-hyperthreading-for-oltp-queries.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://sqlblog.com/aggbug.aspx?PostID=40853" width="1" height="1"&gt;</description><enclosure url="http://sqlblog.com/blogs/linchi_shea/attachment/40853.ashx" length="1455" type="application/x-zip-compressed" /><category domain="http://sqlblog.com/blogs/linchi_shea/archive/tags/Performance/default.aspx">Performance</category><category domain="http://sqlblog.com/blogs/linchi_shea/archive/tags/Testing/default.aspx">Testing</category><category domain="http://sqlblog.com/blogs/linchi_shea/archive/tags/Query+Processing/default.aspx">Query Processing</category><category domain="http://sqlblog.com/blogs/linchi_shea/archive/tags/Benchmark/default.aspx">Benchmark</category><category domain="http://sqlblog.com/blogs/linchi_shea/archive/tags/TPC-C/default.aspx">TPC-C</category><category domain="http://sqlblog.com/blogs/linchi_shea/archive/tags/hyperthreading/default.aspx">hyperthreading</category></item><item><title>Performance impact: hyperthreading for reporting queries</title><link>http://sqlblog.com/blogs/linchi_shea/archive/2012/01/05/performance-impact-hyperthreading-for-reporting-queries.aspx</link><pubDate>Thu, 05 Jan 2012 05:36:00 GMT</pubDate><guid isPermaLink="false">21093a07-8b3d-42db-8cbf-3350fcbf5496:40817</guid><dc:creator>Linchi Shea</dc:creator><slash:comments>16</slash:comments><comments>http://sqlblog.com/blogs/linchi_shea/comments/40817.aspx</comments><wfw:commentRss>http://sqlblog.com/blogs/linchi_shea/commentrss.aspx?PostID=40817</wfw:commentRss><description>There are a lot of questions on hyperthreading, but not a lot of answers. There is no shortage of opinions, but very few are based on significant first hand experience or solid test data. We know that the hyperthreading technology in the older generations...(&lt;a href="http://sqlblog.com/blogs/linchi_shea/archive/2012/01/05/performance-impact-hyperthreading-for-reporting-queries.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://sqlblog.com/aggbug.aspx?PostID=40817" width="1" height="1"&gt;</description><enclosure url="http://sqlblog.com/blogs/linchi_shea/attachment/40817.ashx" length="1381" type="application/x-zip-compressed" /><category domain="http://sqlblog.com/blogs/linchi_shea/archive/tags/Performance/default.aspx">Performance</category><category domain="http://sqlblog.com/blogs/linchi_shea/archive/tags/Benchmark/default.aspx">Benchmark</category><category domain="http://sqlblog.com/blogs/linchi_shea/archive/tags/parallelism/default.aspx">parallelism</category><category domain="http://sqlblog.com/blogs/linchi_shea/archive/tags/hyperthreading/default.aspx">hyperthreading</category><category domain="http://sqlblog.com/blogs/linchi_shea/archive/tags/Reporting+queries/default.aspx">Reporting queries</category><category domain="http://sqlblog.com/blogs/linchi_shea/archive/tags/HT/default.aspx">HT</category></item><item><title>Evaluating server hardware: a sign of the times</title><link>http://sqlblog.com/blogs/linchi_shea/archive/2012/01/03/evaluating-server-hardware-a-sign-of-the-times.aspx</link><pubDate>Tue, 03 Jan 2012 05:02:20 GMT</pubDate><guid isPermaLink="false">21093a07-8b3d-42db-8cbf-3350fcbf5496:40750</guid><dc:creator>Linchi Shea</dc:creator><slash:comments>7</slash:comments><comments>http://sqlblog.com/blogs/linchi_shea/comments/40750.aspx</comments><wfw:commentRss>http://sqlblog.com/blogs/linchi_shea/commentrss.aspx?PostID=40750</wfw:commentRss><description>For nearly ten years, I have had success in using a specifically modified version of the TPC-C benchmark for evaluating server hardware running SQL Server. Depending on your purpose, you can evaluate computer hardware in numerous ways with numerous benchmarks....(&lt;a href="http://sqlblog.com/blogs/linchi_shea/archive/2012/01/03/evaluating-server-hardware-a-sign-of-the-times.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://sqlblog.com/aggbug.aspx?PostID=40750" width="1" height="1"&gt;</description><category domain="http://sqlblog.com/blogs/linchi_shea/archive/tags/Performance/default.aspx">Performance</category><category domain="http://sqlblog.com/blogs/linchi_shea/archive/tags/Benchmark/default.aspx">Benchmark</category><category domain="http://sqlblog.com/blogs/linchi_shea/archive/tags/Many-core/default.aspx">Many-core</category><category domain="http://sqlblog.com/blogs/linchi_shea/archive/tags/TPC-C/default.aspx">TPC-C</category></item><item><title>Performance impact: a little business logic goes a long way</title><link>http://sqlblog.com/blogs/linchi_shea/archive/2011/12/23/performance-impact-a-little-business-logic-goes-a-long-way.aspx</link><pubDate>Fri, 23 Dec 2011 05:13:21 GMT</pubDate><guid isPermaLink="false">21093a07-8b3d-42db-8cbf-3350fcbf5496:40606</guid><dc:creator>Linchi Shea</dc:creator><slash:comments>2</slash:comments><comments>http://sqlblog.com/blogs/linchi_shea/comments/40606.aspx</comments><wfw:commentRss>http://sqlblog.com/blogs/linchi_shea/commentrss.aspx?PostID=40606</wfw:commentRss><description>I’m running into this little performance tuning pattern enough number of times that it is worth a special mention. As it often happens, the app folks complain about a proc call being very slow, and I track it down to a specific line in the proc. The line...(&lt;a href="http://sqlblog.com/blogs/linchi_shea/archive/2011/12/23/performance-impact-a-little-business-logic-goes-a-long-way.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://sqlblog.com/aggbug.aspx?PostID=40606" width="1" height="1"&gt;</description><category domain="http://sqlblog.com/blogs/linchi_shea/archive/tags/Performance/default.aspx">Performance</category><category domain="http://sqlblog.com/blogs/linchi_shea/archive/tags/Business+logic/default.aspx">Business logic</category></item><item><title>Performance impact: diminishing marginal return on the degree of parallelism</title><link>http://sqlblog.com/blogs/linchi_shea/archive/2011/12/16/performance-impact-diminishing-marginal-return-on-the-degree-of-parallelism.aspx</link><pubDate>Fri, 16 Dec 2011 17:24:00 GMT</pubDate><guid isPermaLink="false">21093a07-8b3d-42db-8cbf-3350fcbf5496:40458</guid><dc:creator>Linchi Shea</dc:creator><slash:comments>25</slash:comments><comments>http://sqlblog.com/blogs/linchi_shea/comments/40458.aspx</comments><wfw:commentRss>http://sqlblog.com/blogs/linchi_shea/commentrss.aspx?PostID=40458</wfw:commentRss><description>In commenting on my previous post , Greg Linwood and GrumpyOldDBA raised questions about various implications of parallelism. In this post, I’ll look at the impact of different degrees of parallelism on the query performance. I’ll limit my examination...(&lt;a href="http://sqlblog.com/blogs/linchi_shea/archive/2011/12/16/performance-impact-diminishing-marginal-return-on-the-degree-of-parallelism.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://sqlblog.com/aggbug.aspx?PostID=40458" width="1" height="1"&gt;</description><enclosure url="http://sqlblog.com/blogs/linchi_shea/attachment/40458.ashx" length="7090" type="application/x-zip-compressed" /><category domain="http://sqlblog.com/blogs/linchi_shea/archive/tags/Performance/default.aspx">Performance</category><category domain="http://sqlblog.com/blogs/linchi_shea/archive/tags/Query+Processing/default.aspx">Query Processing</category><category domain="http://sqlblog.com/blogs/linchi_shea/archive/tags/parallelism/default.aspx">parallelism</category></item><item><title>Performance impact: Cartesian product comes to the rescue</title><link>http://sqlblog.com/blogs/linchi_shea/archive/2011/12/15/performance-impact-cartesian-product-comes-to-the-rescue.aspx</link><pubDate>Thu, 15 Dec 2011 06:11:00 GMT</pubDate><guid isPermaLink="false">21093a07-8b3d-42db-8cbf-3350fcbf5496:40419</guid><dc:creator>Linchi Shea</dc:creator><slash:comments>10</slash:comments><comments>http://sqlblog.com/blogs/linchi_shea/comments/40419.aspx</comments><wfw:commentRss>http://sqlblog.com/blogs/linchi_shea/commentrss.aspx?PostID=40419</wfw:commentRss><description>Although Cartesian product as a concept is essential to the relational database theory, it is often a dirty phrase – something that is associated with bad performance and therefore should be avoided. But there are cases where a Cartesian product is highly...(&lt;a href="http://sqlblog.com/blogs/linchi_shea/archive/2011/12/15/performance-impact-cartesian-product-comes-to-the-rescue.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://sqlblog.com/aggbug.aspx?PostID=40419" width="1" height="1"&gt;</description><enclosure url="http://sqlblog.com/blogs/linchi_shea/attachment/40419.ashx" length="1324" type="application/x-zip-compressed" /><category domain="http://sqlblog.com/blogs/linchi_shea/archive/tags/Performance/default.aspx">Performance</category><category domain="http://sqlblog.com/blogs/linchi_shea/archive/tags/Query+Processing/default.aspx">Query Processing</category></item><item><title>Performance impact: synchronous audit can trash your database performance – III</title><link>http://sqlblog.com/blogs/linchi_shea/archive/2011/12/13/performance-impact-synchronous-audit-can-trash-your-database-performance-iii.aspx</link><pubDate>Wed, 14 Dec 2011 02:52:00 GMT</pubDate><guid isPermaLink="false">21093a07-8b3d-42db-8cbf-3350fcbf5496:40373</guid><dc:creator>Linchi Shea</dc:creator><slash:comments>0</slash:comments><comments>http://sqlblog.com/blogs/linchi_shea/comments/40373.aspx</comments><wfw:commentRss>http://sqlblog.com/blogs/linchi_shea/commentrss.aspx?PostID=40373</wfw:commentRss><description>This is the third installment of my posts on the performance impact of enabling SQL Server 2008 R2 Audit. My previous two posts ( part I and part II ) show that whether it’s on a two-processor machine or an eight-processor machine, enabling an audit with...(&lt;a href="http://sqlblog.com/blogs/linchi_shea/archive/2011/12/13/performance-impact-synchronous-audit-can-trash-your-database-performance-iii.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://sqlblog.com/aggbug.aspx?PostID=40373" width="1" height="1"&gt;</description><category domain="http://sqlblog.com/blogs/linchi_shea/archive/tags/Performance/default.aspx">Performance</category><category domain="http://sqlblog.com/blogs/linchi_shea/archive/tags/Audit/default.aspx">Audit</category></item><item><title>Performance impact: synchronous audit can trash your database performance – II</title><link>http://sqlblog.com/blogs/linchi_shea/archive/2011/12/12/performance-impact-synchronous-audit-can-trash-your-database-performance-ii.aspx</link><pubDate>Tue, 13 Dec 2011 02:58:00 GMT</pubDate><guid isPermaLink="false">21093a07-8b3d-42db-8cbf-3350fcbf5496:40298</guid><dc:creator>Linchi Shea</dc:creator><slash:comments>1</slash:comments><comments>http://sqlblog.com/blogs/linchi_shea/comments/40298.aspx</comments><wfw:commentRss>http://sqlblog.com/blogs/linchi_shea/commentrss.aspx?PostID=40298</wfw:commentRss><description>In my previous post on this subject, I showed the test results from a two-processor machine. Naturally, you may wonder: do we expect to see the same dramatic throughput drop when we enable a synchronous audit (i.e. with the queue_delay property set to...(&lt;a href="http://sqlblog.com/blogs/linchi_shea/archive/2011/12/12/performance-impact-synchronous-audit-can-trash-your-database-performance-ii.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://sqlblog.com/aggbug.aspx?PostID=40298" width="1" height="1"&gt;</description><category domain="http://sqlblog.com/blogs/linchi_shea/archive/tags/Performance/default.aspx">Performance</category><category domain="http://sqlblog.com/blogs/linchi_shea/archive/tags/Audit/default.aspx">Audit</category></item><item><title>Multiple independent results from a single SELECT statement</title><link>http://sqlblog.com/blogs/linchi_shea/archive/2011/12/12/multiple-independent-results-from-a-single-select-statement.aspx</link><pubDate>Mon, 12 Dec 2011 20:39:00 GMT</pubDate><guid isPermaLink="false">21093a07-8b3d-42db-8cbf-3350fcbf5496:40284</guid><dc:creator>Linchi Shea</dc:creator><slash:comments>4</slash:comments><comments>http://sqlblog.com/blogs/linchi_shea/comments/40284.aspx</comments><wfw:commentRss>http://sqlblog.com/blogs/linchi_shea/commentrss.aspx?PostID=40284</wfw:commentRss><description>You cannot output multiple independent results from a single SELECT statement. But sometimes I wish that could be done. An extremely simple case is when you need to build the initial dimensions from a very large table. Typically, these dimension columns...(&lt;a href="http://sqlblog.com/blogs/linchi_shea/archive/2011/12/12/multiple-independent-results-from-a-single-select-statement.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://sqlblog.com/aggbug.aspx?PostID=40284" width="1" height="1"&gt;</description><category domain="http://sqlblog.com/blogs/linchi_shea/archive/tags/Performance/default.aspx">Performance</category><category domain="http://sqlblog.com/blogs/linchi_shea/archive/tags/T-SQL/default.aspx">T-SQL</category></item><item><title>Performance impact: synchronous audit can trash your database performance</title><link>http://sqlblog.com/blogs/linchi_shea/archive/2011/12/11/performance-impact-synchronous-audit-can-trash-your-database-performance.aspx</link><pubDate>Sun, 11 Dec 2011 22:26:00 GMT</pubDate><guid isPermaLink="false">21093a07-8b3d-42db-8cbf-3350fcbf5496:40266</guid><dc:creator>Linchi Shea</dc:creator><slash:comments>3</slash:comments><comments>http://sqlblog.com/blogs/linchi_shea/comments/40266.aspx</comments><wfw:commentRss>http://sqlblog.com/blogs/linchi_shea/commentrss.aspx?PostID=40266</wfw:commentRss><description>The SQL Server Audit feature introduced in SQL Server2008 is useful in many scenarios. Although it still has much room for improvement , it has made SQL Server auditing easier to manage, and in particular, it has reduced performance impact as compared...(&lt;a href="http://sqlblog.com/blogs/linchi_shea/archive/2011/12/11/performance-impact-synchronous-audit-can-trash-your-database-performance.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://sqlblog.com/aggbug.aspx?PostID=40266" width="1" height="1"&gt;</description><category domain="http://sqlblog.com/blogs/linchi_shea/archive/tags/Performance/default.aspx">Performance</category><category domain="http://sqlblog.com/blogs/linchi_shea/archive/tags/Audit/default.aspx">Audit</category></item><item><title>Transactional replication and massive data updates</title><link>http://sqlblog.com/blogs/linchi_shea/archive/2011/10/06/transactional-replication-and-massive-data-updates.aspx</link><pubDate>Thu, 06 Oct 2011 04:19:00 GMT</pubDate><guid isPermaLink="false">21093a07-8b3d-42db-8cbf-3350fcbf5496:38876</guid><dc:creator>Linchi Shea</dc:creator><slash:comments>4</slash:comments><comments>http://sqlblog.com/blogs/linchi_shea/comments/38876.aspx</comments><wfw:commentRss>http://sqlblog.com/blogs/linchi_shea/commentrss.aspx?PostID=38876</wfw:commentRss><description>SQL Server transactional replication has been a rather solid feature and works well for delivering data to reporting servers (among other things) in near real time. That said, it may not work too well when you need to perform massive updates on a published...(&lt;a href="http://sqlblog.com/blogs/linchi_shea/archive/2011/10/06/transactional-replication-and-massive-data-updates.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://sqlblog.com/aggbug.aspx?PostID=38876" width="1" height="1"&gt;</description><category domain="http://sqlblog.com/blogs/linchi_shea/archive/tags/Performance/default.aspx">Performance</category><category domain="http://sqlblog.com/blogs/linchi_shea/archive/tags/Scripting/default.aspx">Scripting</category><category domain="http://sqlblog.com/blogs/linchi_shea/archive/tags/Replication/default.aspx">Replication</category></item><item><title>Performance impact: Don’t assume they are the same</title><link>http://sqlblog.com/blogs/linchi_shea/archive/2011/10/01/performance-impact-don-t-assume-they-are-the-same.aspx</link><pubDate>Sat, 01 Oct 2011 15:42:00 GMT</pubDate><guid isPermaLink="false">21093a07-8b3d-42db-8cbf-3350fcbf5496:38812</guid><dc:creator>Linchi Shea</dc:creator><slash:comments>3</slash:comments><comments>http://sqlblog.com/blogs/linchi_shea/comments/38812.aspx</comments><wfw:commentRss>http://sqlblog.com/blogs/linchi_shea/commentrss.aspx?PostID=38812</wfw:commentRss><description>When you deploy a production cluster, you want any failover to be as transparent to your users as possible. It follows that the nodes within the cluster should be identical in terms of their hardware and software configurations. It further follows that...(&lt;a href="http://sqlblog.com/blogs/linchi_shea/archive/2011/10/01/performance-impact-don-t-assume-they-are-the-same.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://sqlblog.com/aggbug.aspx?PostID=38812" width="1" height="1"&gt;</description><category domain="http://sqlblog.com/blogs/linchi_shea/archive/tags/Performance/default.aspx">Performance</category><category domain="http://sqlblog.com/blogs/linchi_shea/archive/tags/Benchmark/default.aspx">Benchmark</category></item><item><title>Performance impact: stored procedures, SQL batches, and CPU usage</title><link>http://sqlblog.com/blogs/linchi_shea/archive/2011/07/22/performance-impact-stored-procedures-sql-batches-and-cpu-usage.aspx</link><pubDate>Fri, 22 Jul 2011 03:47:00 GMT</pubDate><guid isPermaLink="false">21093a07-8b3d-42db-8cbf-3350fcbf5496:37234</guid><dc:creator>Linchi Shea</dc:creator><slash:comments>4</slash:comments><comments>http://sqlblog.com/blogs/linchi_shea/comments/37234.aspx</comments><wfw:commentRss>http://sqlblog.com/blogs/linchi_shea/commentrss.aspx?PostID=37234</wfw:commentRss><description>What is the simplest way to drive a CPU to 100% using T-SQL? If it’s a language like C++ or C#, the simplest way is to create a tight loop and perform some work that uses CPU cycles inside the loop. For instance, the following tight loop in C# can peg...(&lt;a href="http://sqlblog.com/blogs/linchi_shea/archive/2011/07/22/performance-impact-stored-procedures-sql-batches-and-cpu-usage.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://sqlblog.com/aggbug.aspx?PostID=37234" width="1" height="1"&gt;</description><category domain="http://sqlblog.com/blogs/linchi_shea/archive/tags/Performance/default.aspx">Performance</category><category domain="http://sqlblog.com/blogs/linchi_shea/archive/tags/batch/default.aspx">batch</category><category domain="http://sqlblog.com/blogs/linchi_shea/archive/tags/Stored+procedures/default.aspx">Stored procedures</category></item></channel></rss>