August 1, 2008 at 8:36 am
I understand SQL Server handles tempdb better in 2005, but do the Microsoft suggestions of creating at least one tempdb data file per CPU still apply in 2005?
http://support.microsoft.com/kb/328551
Thanks, Dave
August 1, 2008 at 8:42 am
as far as I know, Yes. That's still considered best practice, one TempDB datafile per core
_____________________________________
Pablo (Paul) Berzukov
Author of Understanding Database Administration available at Amazon and other bookstores.
Disclaimer: Advice is provided to the best of my knowledge but no implicit or explicit warranties are provided. Since the advisor explicitly encourages testing any and all suggestions on a test non-production environment advisor should not held liable or responsible for any actions taken based on the given advice.August 1, 2008 at 10:36 am
The datafiles piece, yes.
But don't rely on that link for SQL 2005, it is outdated. For example, implementing trace flag -T1118 is not applicable.
Check out these links instead:
Configure SQL Server 2005 TempDB for performance
http://searchsqlserver.techtarget.com/tip/1,289483,sid87_gci1180698_tax301334,00.html?bucket=ETA
Working with tempdb in SQL Server 2005
http://www.microsoft.com/technet/prodtechnol/sql/2005/workingwithtempdb.mspx#ECNAC
Troubleshooting Insufficient Disk Space in tempdb
http://msdn2.microsoft.com/en-us/library/ms176029.aspx
Capacity Planning for tempdb
http://msdn2.microsoft.com/en-us/library/ms345368.aspx
__________________________________________________________________________________
SQL Server 2016 Columnstore Index Enhancements - System Views for Disk-Based Tables[/url]
Persisting SQL Server Index-Usage Statistics with MERGE[/url]
Turbocharge Your Database Maintenance With Service Broker: Part 2[/url]
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply