Link to home
Start Free TrialLog in
Avatar of bizjosh
bizjoshFlag for Singapore

asked on

SharePoint 2007 Content Databases becoming more than 100GB

I have 20 Site Collections and 1 Content Database which is becoming more than 100GB.

What is the best approach to handle this i.e. Content DB split? Do i need to change my architecture? Need to consider MOSS2010 upgrade in 2011 as well.

 I need recommendations of steps architecturally to ensure:

- least impact to the business users
- no URL change if possible
- scalability so we wont have to split again in future

Please do not paste links that you are unsure and does not give me the above solution points.

Thanks!
Avatar of luceysupport
luceysupport
Flag of Ireland image

Simply set the current content database to offline (this means no new sites will be created in it) and add a new one. All new sites will be added to the new content db. Do this all in Content Databases within application management in central admin, make sure to select the correct web app.

You can, if you want, use stsadm to transfer existing site collections from one content db to another without impacting urls.

Do this before getting to 100Gb in future. When creating your content db set the max number of sites and the warining level. Use quotas to manage the size of sites and you should be able to pre-emt any problems with db size.

I hope this helps
Avatar of bizjosh

ASKER

Won't the new sites created in the site collection be on a different URL?
No, just the content will be in a different database.

You can add multiple content databases to the same web application and hence not change the url of the web application.

ASKER CERTIFIED SOLUTION
Avatar of FFNetAdmins
FFNetAdmins
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Hi,

Just one comment - setting the database to offline and adding a new database will ensure that the new site collections will be created in this new db. However, a sub-site created in an existing site collection, will go into the initial database. A site collection cannot be split into multiple databases.

I agree with FFNetAdmins - you can move some of the site collections using stsamd -o backup/restore rather easy.

Avatar of bizjosh

ASKER

Hmm. 8 of my site collections are 80GB each. It will grow into 100GB soon.

I need to split my site collection but can i do it without changing url?
Exacty.
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of bizjosh

ASKER

Can you please explain how i can keep the same URL?
Let's say your subsite is named http://root/sites/site1/site2
You can backup site2 (stsadm -o export), rename site2 let's say to site2old, create an explicit managed path "sites/site1/site2", create a new site collection at this new managed path (i'm using blank template, to avoid issues at restore caused by the default libraries/lists that get created), then restore backup over this new site (stsadm -o import).

There is a recommended limit to the number of managed paths per web application (sorry, don't remember the exact link or number), so it is good to do an analysis before breaking the site collection, so that you don't split the site collection into too many pieces.
 
This question has been classified as abandoned and is closed as part of the Cleanup Program. See the recommendation for more details.