InstantForum.NET v2.9.0SQLServerCentralhttp://www.sqlservercentral.com/Forums/notifications@sqlservercentral.comThu, 23 May 2013 20:22:00 GMT20http://www.sqlservercentral.com/Forums/Topic990062-5-1.aspxThat advice has been floating around for a while and is really only applicable when you have identified bottlenecks in the tempdb.some good advice about this here[url] http://www.sqlskills.com/BLOGS/PAUL/post/A-SQL-Server-DBA-myth-a-day-(1230)-tempdb-should-always-have-one-data-file-per-processor-core.aspx [/url]Mon, 15 Nov 2010 06:54:33 GMTsteveb. http://www.sqlservercentral.com/Forums/Topic990062-5-1.aspxBefore you consider implementing that, read this: [url]http://sqlskills.com/BLOGS/PAUL/post/A-SQL-Server-DBA-myth-a-day-(1230)-tempdb-should-always-have-one-data-file-per-processor-core.aspx[/url]Mon, 15 Nov 2010 06:53:22 GMTGilaMonsterhttp://www.sqlservercentral.com/Forums/Topic990062-5-1.aspxThanks for the reply.Sorry for my late response.Have you implimented ever before or if you have any document how to set it? please advise.Thanks in advance.Regards,Ravichandra.Mon, 15 Nov 2010 06:16:48 GMTravisamigohttp://www.sqlservercentral.com/Forums/Topic990062-5-1.aspxEssentially what this is saying is that, for optimal performance, you could add data files of the same size to tempdb up to the # of processors on your server. So a 4 processor server should have 4 same-sized physical files for tempdb for optimal tempdb performance. The reason you want the files to be the same size is because SQL Server tries to keep the files filled to the same proportion. So if you had a 100MB file and a 200MB file, SQL Server will try to keep them at the same fill level, for example 50%, which means that the 200MB file will be written to approximately twice as much as the 100MB file which reduces the performance gained by having multiply files.Tue, 21 Sep 2010 06:16:36 GMT Jack Corbetthttp://www.sqlservercentral.com/Forums/Topic990062-5-1.aspxDear All,Can someone advise/suggest on the below? Please “The number of data files you should allocate in the tempdb database will depend on the number of CPUs (logical or physical) present in the machine. When SQL Server accesses a database, it starts a scheduler thread for each data file present. So if you have eight CPUs in your physical server, the tempdb database should have eight data files to “load balance” the threadsAlso, data files in a database are used in a “proportional fill” algorithm. This means that if you have two data files in a database – one 4 GB and another 8 GB, SQL will try to stripe the data across the two files in a 1:2 ratio. For each stripe of data written to the 4 GB file, SQL will write two stripes in the 8GB file – hence the term “proportional fill”. Now if you configure tempdb to have the same number of data files as the number of CPUs present and specify each data file to have the same size and growth, you are effectively ensuring the CPU load is evenly distributed across tempdb. Once you have completed the tempdb configuration, you will need to restart the SQL instance for the changes to take effect.”You can find Step 5: Configure tempdb Database point from the below link for your reference.http://www.sql-server-performance.com/articles/dba/post_installation_steps_p1.aspxThanks and Regards,Ravichandra.Tue, 21 Sep 2010 03:05:02 GMTravisamigo