One data file per CPU.. Why ?

They say tempdb requires one data file per CPU. Why ?
Also, why just tempdb ? Why not every user database to have the same
requirement of one data file per CPU?
ThanksWho is "they say"? If youa re referring to the KBs that MS put out they
actually explain why. But in a nutshell it is because tempdb by nature
creates a lot of new tables and extents where as a user db normally only
creates new objects occasionally. There is contention on the portion of the
file that holds this information when you create lots of new objects
concurrently in SQL2000. Each file has its own allocation unit so you
effectively spread the load across each of the files. But I would read the
articles for more details.
Andrew J. Kelly SQL MVP
"Hassan" <Hassan@.hotmail.com> wrote in message
news:OEXgpr1NHHA.4376@.TK2MSFTNGP03.phx.gbl...
> They say tempdb requires one data file per CPU. Why ?
> Also, why just tempdb ? Why not every user database to have the same
> requirement of one data file per CPU?
> Thanks
>|||Hi Hassan
To add to Andrews suggestion as well as the KB issue on this I suggest you
also read Kalen Delaney's "Inside Microsoft SQL Server 2005: The Storage
Engine" ISBN 0735621055
John