SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. Join them; it only takes a minute:

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've got a site which has a 2007 content database around 165GB at present they're running out of space on the SQL server so I'm just going to advise we move them all to a new SQL Server 2008 R2 database server with ample space.

After which the customer is considering migrating to SharePoint 2010, I'm a little aprehensive about kicking off the migration on such a large content DB, but I suspect it would probably go through but just take a fairly long time.

The other option is we work on getting the size of the primary content DB down to around 100GB and attempt it then. I'll get the WFE on Server 2008 R2 and kick off an inplace upgrade and cross my fingers I think. (with backups in place obviously)

Has anyone attempted or know of any MS literature that advises against doing the upgrade on with such a large content DB?

share|improve this question

165 Gb is indeed, quite some db. There are no problems migrating such a database, its only against the advise of microsoft. It's not that it is not supported

I would do the following:

  1. bring down your GB size to some smaller proportions. Some options are:

    • delete old site collections/sites (ask the owners to do it themselves)
    • delete old versions of files. You could determine to delete every version older then a year, and max 3 or 5 versions per file (again: discuss with the owners, and tell why it's important)
  2. detach/attach your data to the SQL Server 2008r2. I wouldn't advise an inplace upgrade of SP2007. ONLY do that when you don't have ANY customizations! Experience teaches us that it will go (badly) wrong when you do that.

share|improve this answer
Thanks for the reply Bas, as it stands the current DB server has run out of space so trying to remove sites / document librarys will no doubt blow the log files out and I'll run out of space. My thoughts are to detach / attach the current 165GB DB then bring it down. Due to the solutions installed on the farm my only option is to do an inplace upgrade which I have a process for and have done on 20 other SharePoint 2007 farms so I know a trick or 2 about how to get that to work. – pigeon Apr 5 '12 at 8:42
Well this site has now lost their WFE, oh the joy. Looks like I'll be doing a restore using databases only.. – pigeon Apr 17 '12 at 12:19
up vote 0 down vote accepted

If anyone is interested this migration went through without any real issues, the upgrade really didn't take any longer if truth be told, probably 3 hours and the 125GB content DB was upgrade successfully.

share|improve this answer

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.