In SharePoint 2010 it is recommended not to use content databases with more than 200 GB (see TechNet). This value is increased since SharePoint 2007, where we should use only 100 GB for a content database. To create a new site collection in its own database, we can use STSADM or PowerShell cmdlets, when we have access to the console of a SharePoint machine. But how can we create a site collection in its own database, when we only have access to central administration?

There are just a few simple steps needed, to achive this. I’ll explain the steps in SharePoint 2010, but it’s the same in SharePoint 2007.

First let’s start central administration. In CA we open “Manage Content Databases”. When we have selected the correct web application, we should see at least one content database.

Click the name of the content database, to see and edit its properties. When the status of the database is set to ‘Ready’, change the status to ‘Offline’.

Click <OK> to save the changes. When the web application has more content databases, repeat this step for each of them.

When you are back in the overview of the content databases click the link <Add a content database>.

Here we create a new content database for our new site collection. Enter the name for the new database and make the necessary adjustments and click <OK> to create the database.

Back in the database overview of our content databases, you should see our new database with the status ‘Started’.

Now, change to the Application Management and click the ‘Create site collections’ link. This step is business as usual. Enter a title, set the Web Site Address, select a site template and enter at least the primary administrator for the new site collection.

Because there is just one content database in this web application with the status ‘Started’, the new site collection is created in this database.

When we set the status of this new content database to ‘Offline’ after the creation of the new site collection, we need to create a new content database, when we need to create another site collection. Alternatively you can set the capacity settings of the content database(s) to 0 for the warning level and to 1 for the maximum number of site collections.

As you have seen, we can create a new site collection it its own content database, when we do not have access to STSADM or PowerShell.