Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Add files to tempdb Expand / Collapse
Author
Message
Posted Monday, March 1, 2010 8:43 AM
Mr or Mrs. 500

Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500

Group: General Forum Members
Last Login: Tuesday, February 18, 2014 12:52 PM
Points: 502, Visits: 750
Following the guidelines to adding tempdb files for each processor, I have added 3 more files to tempdb through the GIU. (I am assuming this is fine). Do I need to restart the service for this to take affect?


Post #874458
Posted Monday, March 1, 2010 8:51 AM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Monday, May 5, 2014 8:20 AM
Points: 201, Visits: 405
according to microsoft - no....
but I still would

don't forget to run

use tempdb
go
sp_helpfile
go




Post #874466
Posted Monday, March 1, 2010 8:55 AM
Mr or Mrs. 500

Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500

Group: General Forum Members
Last Login: Tuesday, February 18, 2014 12:52 PM
Points: 502, Visits: 750
Am I also correct in assuming you just add data files, not log files?
Thanks



Post #874468
Posted Monday, March 1, 2010 8:58 AM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Monday, May 5, 2014 8:20 AM
Points: 201, Visits: 405
usually yes...
recomendation is one data file per cpu
all them sjould be the same size



Post #874472
Posted Tuesday, March 2, 2010 7:04 AM
SSCommitted

SSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommitted

Group: General Forum Members
Last Login: Monday, October 27, 2014 8:55 AM
Points: 1,639, Visits: 1,985
You should also keep in mind that if one auto grows that SQL will no longer balance the load across the different files properly. Our recommendation to our clients is to make the tempDB files big enough it won't fill up and then turn off autoshrink and autogrow. If that's not an option for you then you'll have to have a way to monitor for grow events on the tempDB and shrink them back to the standard size.
Post #875116
Posted Tuesday, March 2, 2010 7:52 AM


SSCarpal Tunnel

SSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal Tunnel

Group: General Forum Members
Last Login: Today @ 9:01 AM
Points: 4,439, Visits: 6,347
cfradenburg (3/2/2010)
You should also keep in mind that if one auto grows that SQL will no longer balance the load across the different files properly. Our recommendation to our clients is to make the tempDB files big enough it won't fill up and then turn off autoshrink and autogrow. If that's not an option for you then you'll have to have a way to monitor for grow events on the tempDB and shrink them back to the standard size.


Not sure either of those is good advice.

Nor is it appropriate to always have 1 file per CPU core. Most systems dont' have sufficient IOPS to server up tempdb and they suffer from head thrashing when having too many files. Makes things worse, not better. also many systems now have 8-32 cores but just a handful of actual CPUs. hyperthreading is another wrinkle...


Best,

Kevin G. Boles
SQL Server Consultant
SQL MVP 2007-2012
TheSQLGuru at GMail
Post #875179
Posted Tuesday, March 2, 2010 9:15 AM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Thursday, October 9, 2014 1:02 PM
Points: 6,032, Visits: 5,284
I *largely* agree with your issues. There is no hard and fast rule about 1 file per core or CPU. An aweful lot depends on your disk subsystem and how the spindles are spread out. For those with local disks 1 file per core/CPU will probably not be useful because you are likely to have trouble breaking that file up accross spindles unless you have a LOT of local disks, which hasn't been my experience. For those with SAN or equivalent this is a lot easier, however you might start at 1/4 and work your way up. The advice about the autogrow/shrink is correct, turn them off. Set all the tempdb files the same size. Like most things, it depends, I've read the number of files should be an evenly divisible of the number of cores. ie: 8 cores, 2 files, 4 files, or 8 files, NOT 3, 5, 6, or 7 files. I wish I could find that article right now..

CEWII
Post #875258
Posted Tuesday, March 2, 2010 9:19 AM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Monday, May 5, 2014 8:20 AM
Points: 201, Visits: 405
here are some links for your info

http://www.tech-recipes.com/rx/2342/sql_server_2005_move_tempdb/
http://www.google.com/search?sourceid=navclient&aq=t&ie=UTF-8&rlz=1T4GFRG_enUS212US233&q=split+tempdb+into+multiple+files

http://support.microsoft.com/kb/328551

http://www.mssqltips.com/tip.asp?tip=1432



Post #875264
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse