locked
Split Single Site Collection into Multiple Content Databases? RRS feed

  • Question

  •  

    I had an interview today with a senior technical person. One of the question he asked regarding content datrabase size. He insisted that he could split a single site collection into multiple content databases and he has been doing that all the time.

     

    This was a big surprise to me and I did more search on line, I found the same answer as I knoew before: you can not split a single site collection into multiple content database. However, you can convert a sub site into a new site collection which is on a different content database. But I don't think this is waht he ment.

     

    Since I was still in the shock (sort of in a funny way), I decide to post this question here for the experts to help me clear out my mind and make sure I really know what I am doing.

     

    Thank you very much.

    Thursday, July 10, 2008 9:03 PM

Answers

  • LOL

     

    That's bolderdash, can't be done.

     

    You can split the content database into multiple files for performance reasons, but you can't have a site collection spanning multiple databases.

     

    End of... :-)

    Thursday, July 10, 2008 9:57 PM

All replies

  • My understanding is the same. 

     

    The only way you could do this is to create the SC then create subsites and have those subsites on sperate contentent DB.  You could not have the same site split.  i think maybe he meant he was adding sites and they were on seperate DB's

     

    Anyway, just because they are Sr. does not make them smarter... Smile

     

    Thursday, July 10, 2008 9:27 PM
  •  

    Thanks for your answer. As far as I know, new sub sites will go with the site collection which will stay which ever it is. SharePoint does not put new sub site into new content database just because the original is off line.

     

    If this is not correct, please let me know.

    Thursday, July 10, 2008 9:36 PM
  • I was thinking he was moving the subsites, not just placing them in an DB.  I don't see how you can place them in another DB on creation without custom coding this.  You can choose your DB for a site collection, but not a subsite.  In 2003 this is another story.  We did have sub sites on seperate databases.

     

    I may be wrong here...I would like to here as well now that you got me confused Smile

    Thursday, July 10, 2008 9:50 PM
  • LOL

     

    That's bolderdash, can't be done.

     

    You can split the content database into multiple files for performance reasons, but you can't have a site collection spanning multiple databases.

     

    End of... :-)

    Thursday, July 10, 2008 9:57 PM