SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Five content DBs are associated with a webapplication and each content DB can store upto 50GB.

We have configured a couple of site quotas as follows:

  • basic_quota (1GB)
  • collab_quota (2GB)
  • Advanced_quota (5GB)
  • Large_quota (10GB)

So whenever, we create a Site Collection we have to use any one of the above.

Lets say we want to create the following Site Collections:

  • 10 x basic_quota (1GB * 10 = 10GB)
  • 5 x collab_quota (2GB * 5 = 10GB)
  • 3 x Advanced_quota (5GB * 3 = 15GB)
  • 2 x Large_quota (10GB * 2 = 20GB)

In this case, SharePoint does not check the later availability, so it will allow us to create the above mentioned Site Collections.

So at the end of day, we have to move some of the Site Collections to another Content DB which can handle this.

We want to avoid this conflict while creating the Site Collections rather than solving this problem later.

What would be the right way to resolve this?

share|improve this question

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.