Not really. Although there many be some small gain in having multiple files
in file group. At least equal to the number of processors in the server. I
would recommend the following layout for data and index.
Assuming four processors, create four files in your primary file group to
hold the data. Preallocate the files as ((the size of the table + growth) *
2)/4 this should give you enough room to grow and reindex the table. Create
a second file group for the nonclustered indexes. This way if you ever want
to move the index file group off to another set of disks you're ready.
"rc" <rc@spam.com> wrote in message
news:v0********************************@4ax.com...
Hi
We run SQL 2000 on Windows 2000. The database has one big table with
approx. 90m rows in it, it also as 4 indexes on it, one of them is a
clustered index. They physical size of the database is approx. 50Gb
I am planing to migrate the database to more powerful server. My
question is on the new server would we get any benefit from have say 5
x10 Gb file for the database as opposed to a single 50GB file.
The database will have exclusive access to RAID 10 array with
dedicated controller for the data, another array for the T.Log
Any thoughts hints would be very helpful
Thanks