Brijesh's Blog

August 7, 2008

How to create dedicated content database for a site collection:

Filed under: Uncategorized — brij28 @ 12:31 pm
Steps to create a new site collection in a new content database:

Let’s assume that I want to create a new dedicated content database for a new site collection. This site collection will have huge contents and it may require database of size 60-80 GB. Also we do not want any of the content databases to grow more than 100 GB (Microsoft recommended content database size). So we decided to create a new dedicated content database for this site collection. Any new site collection after this must be created in a content database with a least number of sites in it, provided it is not crossing the limit of maximum allowed sites in that content database. 

As usual, I have taken few screen captures for better understanding of this scenario.

We have total 8 content databases for our MOSS 2007 deployment. I have created a new content database with the name “New_Content_DB”.

I want to create a new site collection in this new content database – “New_Content_DB” and then lock it. So that any new site collection after this will be created in a content database (any one from SPS01 to SPS08) with least number of sites in it. Let’s create a new site collection,

New site collection – “sites/newsc” was created in “New_Content_DB” as expected. Now, I would like to lock it so this content database will be used only for this site collection – “sites/newsc”.

I ran following query to confirm that the site collection – “sites/newsc” was created in “New_Content_DB” database.

Now, let’s lock it. I have set “Site Level Warning” to 0 and “Maximum Number of Sites” to 1 for this. Here is the screen capture,

Any new site collection after this must be created in content database with least number of sites in it. In our case it is SPS07. So let’s create a second site collection and it must be created in SPS07 instead of New_Content_DB. Here is the screen capture,

As shown below, the second site collection – “sites/newsc2” was created in SPS07 database.

One more time, SQL query to confirm that second site collection – “sites/newsc2” was created in SPS07 database.

Any new site collection after this point will be created in SPS07 and then SPS08 and so on…Here is the screen capture after creating couple of other site collections – “sites/newsc3”, “sites/newsc4” etc.

As per Microsoft recommendation SharePoint content database should not grow more than 100 GB in size. So you may want to move site collections with maximum contents or fastest growth from one content database to another (the smallest content database in your SharePoint farm or a new content database). Here are the few support links which can help you achieving this.

For SharePoint 2007:

First Release of the Microsoft SharePoint Administration Toolkit:
http://blogs.msdn.com/sharepoint/archive/2008/04/30/announcing-the-first-release-of-the-microsoft-sharepoint-administration-toolkit.aspx

Mergecontentdbs: Stsadm operation:
http://technet.microsoft.com/en-us/library/cc288557.aspx

One of the best posts for moving site collections to another content database:
http://www.toddklindt.com/blog/Lists/Posts/Post.aspx?List=56f96349-3bb6-4087-94f4-7f95ff4ca81f&ID=53

For SharePoint 2003:

MS IT Database Split for WSS2.0 and SPS2003:
http://www.codeplex.com/Release/ProjectReleases.aspx?ProjectName=governance&ReleaseId=5351

Advertisements

Leave a Comment »

No comments yet.

RSS feed for comments on this post. TrackBack URI

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

Create a free website or blog at WordPress.com.

%d bloggers like this: