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.

 All Forums
 SQL Server 2000 Forums
 SQL Server Administration (2000)
 Datafile Advice

Author  Topic 

ricky_newbee
Posting Yak Master

126 Posts

Posted - 2006-06-08 : 09:51:31
Hello,
Can any one please suggest me creating a 80GB datafile.
I have a 80 Gig database and am moving to new server. Here is what i have from my old server 1 mdf 5MB, 5 ndf's 5MB each and 1 ndf 81920MB.
So, my plan is to backup from old server to restore it on new server.
Any suggestions about 80GB ndf?

Thanks,
rick

nr
SQLTeam MVY

12543 Posts

Posted - 2006-06-08 : 09:55:40
Do you mean you want to make a single data file? The file shrink thiung has an option to move data out of a file so you can delete it.
I would do that after the restore so you still have the old system if it fails.

==========================================
Cursors are useful if you don't know sql.
DTS can be used in a similar way.
Beer is not cold and it isn't fizzy.
Go to Top of Page

ricky_newbee
Posting Yak Master

126 Posts

Posted - 2006-06-08 : 09:59:22
nigel,
Thanks. What i was thinking was if its a good idea to keep 80gig ndf? or create multiple ndf's say 10gig each.
Go to Top of Page

Westley
Posting Yak Master

229 Posts

Posted - 2006-06-09 : 05:16:45
Hi Ricky,
I normally keep 10G, or 20G, so for a 80G data, I will heva 4x20G or 8x10G, just the way I got used to, not too sure if there are any good affect on the system, maybe someone can tell me as well :)
Go to Top of Page

rockmoose
SQL Natt Alfen

3279 Posts

Posted - 2006-06-09 : 17:17:55
For performance reasons it is good to split the data across several physical disks.
The different files can be placed on different disks and increase system throughput.

It is also possible to do partial backups and restores of specific files or filegroups in the database,
for large systems this can be necessary.

If you have "read only" data this can be put on a "read only" filegroup, might give some performance boost.

What I usually do is have one file per filegroup, and organize the tables and indexes on these filegroups, and try to spread them over different physical disks.

rockmoose

Go to Top of Page
   

- Advertisement -