Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have a 180GB MOSS 2007 database whose maintenance (i.e. backups and restores) are becoming a problem. Part of the issue can be resolved by splitting the three content sites down into their own site collections, however this will likely still leave me with a 100gb DB to deal with. Whilst this isnt entirely problematic for SQL it does mean that backups / restores take far too long.

my idea is to split each of the databases to 30gb files, then to import the content into them which should distribute the content across the file groups,making it much easier / faster to backup/restore.

Is there a way to backup from a single file and restore to a filegroup?

If i have the wrong understanding of filegroups then I'm more than happy to find out other methods of managing the size of databases.

SQL Server: 2008 64 Bit on Windows 2008

share|improve this question
what version of SQL Server? – MattB May 24 '10 at 14:02
up vote 2 down vote accepted


You'll have to restore then split up the tables/indexes onto filegroups as needed.

  • A backup consists of data pages: there is no logic of this table or that index to allocate to filegroups as required (hence the dearth of object level restore utilities)
  • The restore process recreates the files from information contained in the backup
share|improve this answer
thanks, I kind of thought so, but wanted to make sure. – Mauro May 25 '10 at 6:39

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.