there is this plan to retire all old servers and we have been tasked with migrating WSS3.0 to SharePoint Foundation 2010.

WSS 3.0 runs on Windows Server 2003 R2 x86, there is no SQL, everything runs on Windows Internal Database (with content database being nearly 100GB)

we plan to utilise SharePoint Foundation 2010 which will also have full SQL 2008 R2, all of course running on 64 bit architecture.

What approach would you suggest for this scenario? All help much appreciated.

  • could you provide details on the nature of the content? (documents, records, discussion threads, metadata, etc.) Commented Feb 13, 2012 at 15:48
  • mostly document libraries containing combination of popular file formats (Office files, PDF, DWG, etc.), got there also couple (literally) of custom lists. all run's on out of the box functinality, there is no custom webparts or anything like that.
    – PabloE
    Commented Feb 13, 2012 at 15:55

1 Answer 1


While 100GB is not the largest SP DB around, it clearly indicates that your organization is a regular user of the SharePoint. To that end, I would recommend a few things:

Start with splitting out SQL to a dedicated server. The reasons are numerous but include

  1. Scalability - the SQL Box can be scaled both in RAM and Disk easily as needed.
  2. Performance. Both SQL and SharePoint devour CPU cycles and RAM. By sharing the same resources, both are slowed.
  3. about a hundred other reasons from Disaster Recovery to backups...

Create 1-3 Virtual Machines for SharePoint, consisting ideally of 2 load balanced Web Front Ends and 1 app server. Virtuals are relatively cheap but do not shortchange them on CPU or RAM.

This approach will allow your SharePoint farm to grow as the usage of it does - not only for your current site but for any future sites as well (i.e. Intranet Publishing, Training sites, etc..) There's a lot in 2010 that you might want to consider leveraging.

One last point, when installing your SP2010 environment, be sure to use a SQL Alias instead of referring directly to the SQL DB Machine\Instance name. This allows for greater flexibility down the road should you need to move the databases to another server.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

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