none
How do you split up a large site collection into multiple smaller content db's? RRS feed

  • Question

  • We have a very large site collection (http://intranet.contoso.com) whose content database has grown too large. We need to find a way to move certain subsites which are very large to new content databases, and maintain the URL structure. For example, http://intranet.contoso.com/sites/HR and http://intranet.contoso.com/sites/IS are 50GB each. How can we move them into their own individual content databases in the same site collection so we can maintain their URL's?

    Thanks in advance.


    Imperfect IT - Because when does anything work the way it's supposed to? http://imperfectit.blogspot.com/
    Friday, June 3, 2011 7:51 PM

Answers

All replies

  • Are you sure you're not a little confused on SharePoint's hierarchy terminology? Based on the URLs you're showing for those sites (/sites/HR and /sites/IS), it looks to me like they're already full site collections and not subsites... (I'm saying this b/c the "/sites" component of their path is likely to be a wildcard managed path, under which site collections are placed). As I look at your info, it looks to me like intranet.contoso.com is the top-level web application's URL (with a site collection at that top-level URL) and IS and HR are site collections beneath it at the "sites" wildcard managed path.

    If that's the case, you just need to create a new content database for that web application and move one of the site collections into that content database (this article has good info on how to do that: http://technet.microsoft.com/en-us/library/cc825328.aspx)

    If your URL info above isn't correct, or if I'm misreading and you're sure that HR and IS are subsites (also known as "webs" in the SharePoint object model), then its going to be much more difficult, because its not very easy to promote a web to a top-level site collection. You may be able to try the Export-SPWeb CMDLET to export the web and import it to a new top-level web within a site collection, but I suspect that won't work very well if those webs are as large as you say they are. You may have to look at a third-party migration tool to see if one of them can be used to promote that much content from a web to a site collection.

    But, based on the info you've got above, it really looks like you're talking about HR and IS as site collections, in which case it shouldn't be too bad to move one into a new content database.

    John


    MCITP and MCTS: SharePoint, Virtualization, Project Server 2007
    My books on Amazon: The SharePoint 2010 Disaster Recovery Guide and The SharePoint 2007 Disaster Recovery Guide.
    My blog: My Central Admin.
    • Proposed as answer by Clayton Cobb Friday, June 3, 2011 10:12 PM
    • Marked as answer by Seven M Friday, June 10, 2011 3:28 AM
    • Unmarked as answer by Imperfect IT Wednesday, June 15, 2011 2:14 PM
    Friday, June 3, 2011 9:06 PM
  • Agree with John.  The URLs you showed are all separate site collections, not subsites, so please clarify if your URLs are wrong, or if you were confused by the site hierarchy.  If those are all separate site collections, then they can all easily be separated out into new content databases.  If they are truly sub-sites, then you (or someone) did not plan this farm properly and will have to pay the piper.
    SharePoint Architect || Microsoft MVP || My Blog
    Planet Technologies || SharePoint Task Force
    Friday, June 3, 2011 10:14 PM
  • Sorry for the confusing URL's. They're not site collections - simply sub sites that grew too large. We're looking at ControlPoint as a solution, but I'm not sure it's going to work either. I agree it wasn't an ideal design Clayton, but we're in the process of trying to fix that.


    Imperfect IT - Because when does anything work the way it's supposed to? http://imperfectit.blogspot.com/
    Monday, June 6, 2011 9:39 PM
  • They aren't site collections. We're trying to break up a content DB with some very large sub-sites.
    Imperfect IT - Because when does anything work the way it's supposed to? http://imperfectit.blogspot.com/
    Wednesday, June 15, 2011 2:15 PM
  • Then you're going to have to consider one of the following options:

    • Manual migration of content into new site collections
    • Export/Import as I mentioned above, with its limitations
    • I think there are some third party tools you can purchase to do this, but I don't know off the top of my head which vendors offer this functionality.

    John


    MCITP and MCTS: SharePoint, Virtualization, Project Server 2007
    My books on Amazon: The SharePoint 2010 Disaster Recovery Guide and The SharePoint 2007 Disaster Recovery Guide.
    My blog: My Central Admin.
    Wednesday, June 15, 2011 3:41 PM