<?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>Managing TempDB in SQL Server: TempDB Configuration</title><link>http://blogs.msdn.com/sqlserverstorageengine/archive/2009/01/04/managing-tempdb-in-sql-server-tempdb-configuration.aspx</link><description>In my previous blogs, I described the types of objects in TempDB and how they are managed. I hope that it provided you with a good working knowledge of TempDB. Now the next question is how do I configure the TempDB for my production workload? In this</description><dc:language>en</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>Managing TempDB in SQL Server: TempDB Configuration | Coded Style</title><link>http://blogs.msdn.com/sqlserverstorageengine/archive/2009/01/04/managing-tempdb-in-sql-server-tempdb-configuration.aspx#9274427</link><pubDate>Mon, 05 Jan 2009 03:06:30 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9274427</guid><dc:creator>Managing TempDB in SQL Server: TempDB Configuration | Coded Style</dc:creator><description>&lt;p&gt;PingBack from &lt;a rel="nofollow" target="_new" href="http://www.codedstyle.com/managing-tempdb-in-sql-server-tempdb-configuration/"&gt;http://www.codedstyle.com/managing-tempdb-in-sql-server-tempdb-configuration/&lt;/a&gt;&lt;/p&gt;
</description></item><item><title>SQL Server Transactions and TEMPDB - DMV a key relationship to optimize the performance</title><link>http://blogs.msdn.com/sqlserverstorageengine/archive/2009/01/04/managing-tempdb-in-sql-server-tempdb-configuration.aspx#9418408</link><pubDate>Fri, 13 Feb 2009 14:28:52 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9418408</guid><dc:creator>SQL Server Security, Performance &amp; Tuning (SSQA.net)</dc:creator><description>&lt;p&gt;How many times in a day you observe the TEMPDB in your SQL Server enviornment? How many times in a week&lt;/p&gt;
</description></item><item><title>re: Managing TempDB in SQL Server: TempDB Configuration</title><link>http://blogs.msdn.com/sqlserverstorageengine/archive/2009/01/04/managing-tempdb-in-sql-server-tempdb-configuration.aspx#9930887</link><pubDate>Tue, 01 Dec 2009 17:18:06 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9930887</guid><dc:creator>WhiteXMas</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;Very useful article. Can you please provide some more explanation:&lt;/p&gt;
&lt;p&gt;1. &amp;quot;Never AutoGrow&amp;quot;: Let assume I have a 4 CPUs Server, using SQL Server 2000. I split tempdb files (MDF + 3 extra Files) in equal file size. The current max tempdb size is 10 GB, I allocate 5 GB to each file so that their combined capacity is 20 GB, double of the current tempdb workload.&lt;/p&gt;
&lt;p&gt;If I set autogrowth option to zero to apply the &amp;quot;Never Autogrow&amp;quot; rule. What would happen if ever the SQL Server runs into a situation where tempdb will need more than 20 GB?&lt;/p&gt;
&lt;p&gt;What is the autogrowth value do you recommend?&lt;/p&gt;
&lt;p&gt;2. Can the templog.LDF be left at the default setting? (1 file, autogrowth 10%, unlimited max size)?&lt;/p&gt;
&lt;p&gt;Thanks you very much in advance for any advice.&lt;/p&gt;
</description></item><item><title>re: Managing TempDB in SQL Server: TempDB Configuration</title><link>http://blogs.msdn.com/sqlserverstorageengine/archive/2009/01/04/managing-tempdb-in-sql-server-tempdb-configuration.aspx#9930957</link><pubDate>Tue, 01 Dec 2009 18:34:02 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9930957</guid><dc:creator>Sunil Agarwal</dc:creator><description>&lt;p&gt;When I said 'never autogrow', I meant don’t &amp;nbsp;let the TempDB grow to its steady state size through auto-grow. You should only use auto-grow as a last resort but not as a strategy. So you must enable auto-grow for emergencies but set your TempDB size appropriately for steady state&lt;/p&gt;
&lt;p&gt;For LDF file, similar to what we have said for data files, you will need to know what is the steady state size of the log file and then configure your TempDB to support that. Yes, just like data file, you should set &amp;nbsp;this to autogrow. &lt;/p&gt;
</description></item><item><title>re: Managing TempDB in SQL Server: TempDB Configuration</title><link>http://blogs.msdn.com/sqlserverstorageengine/archive/2009/01/04/managing-tempdb-in-sql-server-tempdb-configuration.aspx#9931139</link><pubDate>Tue, 01 Dec 2009 23:07:31 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9931139</guid><dc:creator>WhiteXMas</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;Thank you very much for your help.&lt;/p&gt;
&lt;p&gt;Understood for Q1. &lt;/p&gt;
&lt;p&gt;As for Q2. I am sorry I was not clear. I meant is there any need to split the tempdb LDF. (create one extra file for LDF per CPU, the same way than what you recommended for MDF).&lt;/p&gt;
&lt;p&gt;Thanks.&lt;/p&gt;
</description></item><item><title>re: Managing TempDB in SQL Server: TempDB Configuration</title><link>http://blogs.msdn.com/sqlserverstorageengine/archive/2009/01/04/managing-tempdb-in-sql-server-tempdb-configuration.aspx#9931173</link><pubDate>Wed, 02 Dec 2009 00:34:16 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9931173</guid><dc:creator>Sunil Agarwal</dc:creator><description>&lt;p&gt;Creating multiple log files does not help allocation contention issue becauase the log is append only which is dfferent from regular data. If you log file does not fit on avaikabel space on the drive, you may create multiple files to meet the capacity&lt;/p&gt;
&lt;p&gt;thanks&lt;/p&gt;
</description></item><item><title>re: Managing TempDB in SQL Server: TempDB Configuration</title><link>http://blogs.msdn.com/sqlserverstorageengine/archive/2009/01/04/managing-tempdb-in-sql-server-tempdb-configuration.aspx#9931174</link><pubDate>Wed, 02 Dec 2009 00:34:21 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9931174</guid><dc:creator>Sunil Agarwal</dc:creator><description>&lt;p&gt;Creating multiple log files does not help allocation contention issue becauase the log is append only which is dfferent from regular data. If you log file does not fit on avaikabel space on the drive, you may create multiple files to meet the capacity&lt;/p&gt;
&lt;p&gt;thanks&lt;/p&gt;
</description></item></channel></rss>