<?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>Reduce the Contention on tempdb with Trace Flag 1118: Take 2</title><link>http://sqlblog.com/blogs/linchi_shea/archive/2007/08/10/reduce-the-contention-on-tempdb-with-trace-flag-1118-take-2.aspx</link><description>My earlier attempt to see what's going on with trace flag 1118 on SQL Server 2005 SP2 (9.00.3042) didn't take me too far because the results were not conclusive. I was motivated by seemingly conflicting suggestions from KB article Q936185 and whitepaper</description><dc:language>en</dc:language><generator>CommunityServer 2.1 SP2 (Build: 61129.1)</generator><item><title>re: Reduce the Contention on tempdb with Trace Flag 1118: Take 2</title><link>http://sqlblog.com/blogs/linchi_shea/archive/2007/08/10/reduce-the-contention-on-tempdb-with-trace-flag-1118-take-2.aspx#7156</link><pubDate>Thu, 05 Jun 2008 13:40:34 GMT</pubDate><guid isPermaLink="false">21093a07-8b3d-42db-8cbf-3350fcbf5496:7156</guid><dc:creator>JohnW</dc:creator><description>&lt;p&gt;I know this is an old post at this point...&lt;/p&gt;
&lt;p&gt;I'm not sure I drew the same conclusion as you did. &amp;nbsp;I can be up to ~18% faster w/o 1118, iff i have a lower load level. &amp;nbsp;But if i have a lower load level, I'm probably not that worried about performance. &amp;nbsp;When I do have a higher load level, I am worried about performance, and ~13% slower would catch my eye.&lt;/p&gt;
</description></item><item><title>re: Reduce the Contention on tempdb with Trace Flag 1118: Take 2</title><link>http://sqlblog.com/blogs/linchi_shea/archive/2007/08/10/reduce-the-contention-on-tempdb-with-trace-flag-1118-take-2.aspx#16996</link><pubDate>Fri, 25 Sep 2009 22:23:00 GMT</pubDate><guid isPermaLink="false">21093a07-8b3d-42db-8cbf-3350fcbf5496:16996</guid><dc:creator>Linchi Shea</dc:creator><description>&lt;p&gt;JohnW;&lt;/p&gt;
&lt;p&gt;Points taken. Of course, it's more critical when the load is high.&lt;/p&gt;
</description></item><item><title>SQL Server challenge: show me trace flag 1118 is significant</title><link>http://sqlblog.com/blogs/linchi_shea/archive/2007/08/10/reduce-the-contention-on-tempdb-with-trace-flag-1118-take-2.aspx#17181</link><pubDate>Thu, 01 Oct 2009 16:22:18 GMT</pubDate><guid isPermaLink="false">21093a07-8b3d-42db-8cbf-3350fcbf5496:17181</guid><dc:creator>Linchi Shea</dc:creator><description>&lt;p&gt;Here is a SQL Server challenge as I have failed so far: Describe a reproducible workload that would see&lt;/p&gt;
</description></item><item><title>SQL Server challenge: show me trace flag 1118 is significant -- a quick update</title><link>http://sqlblog.com/blogs/linchi_shea/archive/2007/08/10/reduce-the-contention-on-tempdb-with-trace-flag-1118-take-2.aspx#17215</link><pubDate>Fri, 02 Oct 2009 20:42:05 GMT</pubDate><guid isPermaLink="false">21093a07-8b3d-42db-8cbf-3350fcbf5496:17215</guid><dc:creator>Linchi Shea</dc:creator><description>&lt;p&gt;I posted the following SQL Server challenge yesterday: Describe a reproducible workload that would see&lt;/p&gt;
</description></item></channel></rss>