November 26, 2012 at 11:52 pm
i read an article 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 where this was quoted
Depends why you're adding files. If you're adding files just to alleviate contention on the allocation pages, they can be on the same drive. If you're adding files because you're bottlenecked on IO, then yes, they need to be separate.
Can anybody put some explanation here, primarily for this
adding files just to alleviate contention on the allocation pages
-------Bhuvnesh----------
I work only to learn Sql Server...though my company pays me for getting their stuff done;-)
November 26, 2012 at 11:58 pm
If you're adding files just to relieve allocation contention, they can be on the same drive. If you're adding files because you have IO contention on TempDB, then adding more files on the same drive will be a waste of time (more files on same drive does not improve IO throughput), hence they need to be on separate drives.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
November 27, 2012 at 12:05 am
GilaMonster (11/26/2012)
allocation contention
Can you please explain this
-------Bhuvnesh----------
I work only to learn Sql Server...though my company pays me for getting their stuff done;-)
November 27, 2012 at 12:14 am
http://www.google.com/search?q=allocation+contention+TempDB
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
November 27, 2012 at 12:19 am
thanks gail
-------Bhuvnesh----------
I work only to learn Sql Server...though my company pays me for getting their stuff done;-)
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply