Hi, In my project, I have one web application which has four content databases and approximately 45 site collections each having multiple subsites in them. As it is a good practice to take care that the size of a content data base doesn't cross 100 gb, i want to know what would be the impact of splitting the content from one content database across more content databases. my requirement is to see that size of each data base doesn't cross 100 gb, and i want to what would be the impact of performing such a split. I also want to know how to split the content from one content db across the existing four content dbs(as already mentioned) Thanks in Advance

Hi there, There is a good number of articles that describe how to split content database into multiple files for performance reasons. This can only work if you have multiple site collections and want to positioned these in multiple content databases. http://technet.microsoft.com/en-us/library/cc825327.aspx (suggest you work through this one and it explains what the procedure means and does) http://vishalseth.com/post/2009/07/16/Getting-Ready-to-split-up-a-very-large-MOSS-2007-Content-DB-into-multiple-content-DBs.aspx (useful as it shows another persons perspective on what they did) This has a direct impact on the performance of your SharePoint implementation as it grows in size and usage. If you place all sites in one site collection, or all site collections in one content database, your content database that hosts the site collections will take more and more strain as it grows over time. Hope this helps Geoff

Thanks for the response Geoff. I'll go through the sites you recommended and will get back to you with another post!

Hi Geoff, The sites you mentioned were really helpful. However, I would like to know the after- effects of performing such moves. I mean to ask, will there be any sort of difference in the before-split and the after-split scenario? And can the procedure which is mentioned in the site http://technet.microsoft.com/en-us/library/cc825327.aspx be used to move content across existing content databases itself and not new content dbs? Thanks in Advance.

Hi there, I mean to ask, will there be any sort of difference in the before-split and the after-split scenario? No, other that the fact in the UI you will have more content dbs listed in the relevant web applications, and that in SQL you will have to manage the backup and permissioning of the new multiple content dbs (for example). And can the procedure which is mentioned in the site http://technet.microsoft.com/en-us/library/cc825327.aspx be used to move content across existing content databases itself and not new content dbs? No, the process above allows you to split content by moving site collections into new content dbs, not existing. If you want to move site collections to another content database which exists then you use Import / Export or Backup / Restore. Cheers Geoff