Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
debug2k
Starting Member
18 Posts |
 Posted - 2004-06-23 : 06:50:27
|
| Hello frens,I have a problem, I wanna add one more data file to my production server, but need to give the management benefits..for that...The data file has more grown 4 GBs...so they need a valid reason...Management folks u know hw they are :)Please help me.Regards,Deepak Uniyal |
|
|
mr_mist
Grunnio
1870 Posts |
Posted - 2004-06-23 : 07:48:12
|
| You might see improved performance.-------Moo. :) |
 |
|
|
mcrowley
Aged Yak Warrior
771 Posts |
Posted - 2004-06-23 : 09:23:39
|
| You can see some better performance, if you can manage to get the new datafile on a different disk spindle. If you have some control over the schema (usually not possible with 3rd party vendors), you can create a new filegroup and place some of the more used indexes in it. This is becoming more and more rare, unfortunately, since disk arrays usually spread your files accross all sorts of disks, and you can not be sure what data is on which spindle.Also, each file in a database gets its very own I/O thread. This may help a little, but I doubt it will be a significant boost. So even if the difference were at all significant, you would need a multi-processor box to take advantage of it.At your size, I would probably not bother creating a new file. I have let my files get up to 10GB, before I split them out, and even then, it is more for esthetics than any other reason. It is a tiny bit easier to shrink them back, if need be. But that need comes up so danged rarely. |
|
|
|
debug2k
Starting Member
18 Posts |
Posted - 2004-06-24 : 07:58:31
|
| Thanks a lot frens....its now clear to me..Best Regards,Deepak Uniyal |
|
|
|
|
|
|
|
|
One Datafile Vs. Multiple Data files