> Note that this doesn't really at all if you put them all on the same
> physical drive.

Well, the main reason for using X number of tempdb data files per socket is
not really to address any disk storage performance problem per se. Rather,
it's to resolve a SQL Server internal contention issue on the shared tempdb
metadata structures (e.g. contention on the allocation pages). So if that
metadata contention is the problem, having a better storage system doesn't
, but having multiple data files on the save drive still s.

Linchi

"Aaron Bertrand [SQL Server MVP]" wrote:

> >>
> So watch your tempdb and create at least one additional tempdb per
> socket or even better per core.
> >>
>
> Note that this doesn't really at all if you put them all on the same
> physical drive.
>
>
>