MOSS Forum

Ask Question   UnAnswered
Home » Forum » MOSS       RSS Feeds

Recommended limit to # of site collections in a web app?

  Asked By: Bryon    Date: Jul 30    Category: MOSS    Views: 1988

We are just building our MOSS server and want to start off on the
right foot. Is there a recommended limit for the number of site
collections in a web app? We are a relatively small company and were
planning for 4 web apps but I don't know whether I should be accounting
for the number of site collections within each web app to tell me when
another is needed.



8 Answers Found

Answer #1    Answered By: David Brown     Answered On: Jul 30

I don't know if it's recommended, but in the v2 space I had one web  app
with around 1500 site  collections in it and it seemed to work fine.
Personally I have as few web apps  as possible so that there are few URL
namespaces for users to remember and I scale with Site Collections. I'm
not sure how many you're expecting to have, but you can easily have
hundreds of Site collections  in a web app  and be just fine.

Answer #2    Answered By: Daamodar Bhadranavar     Answered On: Jul 30

According to Microsoft, you can have up to 50,000 Site collections  in a
single web  application. The bigger question I think you should be asking
yourself is, how many Site Collections do you want to put in any single
content database? When you look at SharePoint from a recovery perspective it
is important to limit  the size of your content databases so that you can
manage your backups and restores. Each Site Collection can only reside in a
single content database, though you can have any number  of collections in a
content db. So, while I can have 50,000 collections in my web app, how many
content databases will that be and how many of those collections will be in
each db?

Answer #3    Answered By: Destiny Lewis     Answered On: Jul 30

Great point. Microsoft also recommends no more than 100 content
databases per Web app.

So, let's assume you don't want databases larger than 100 GB (as Daniel
alluded to below), and your site  collections had an average of 10GB
quotas - you could have 10 site collections  per content database (not
including 2nd stage Recycle Bin)

Using some simple math and introducing a reality check, that's actually
about 1,000 site collections per Web app. Well under 50,000. Change the
numbers above and recalculate for your implementation.

Answer #4    Answered By: Tanisha Rowe     Answered On: Jul 30

Okay - I understand the math recommended  but I'm a little lost. When I
create a web  app, I define a content database. When I create a site
collection, I select which web app  to put it in. That part is easy.

Where do I go to create a new database within the same web app?

Answer #5    Answered By: Sierra Lewis     Answered On: Jul 30

You can create additional content databases in Central Admin on the
Application Management page under Content Databases in the Web
Application section of the page. When you create a new site  Collection
it automatically goes into the Content Database with the fewest Sites.
You can control which Content Database it is placed in by taking all the
content Databases but one 'Offline' before creating the new Site
Collection. Offline Databases aren't really Offline, the act normally
except for the fact that you can't create a new Site Collection in them.
Once the Site Collection is created all sites in that collection will be
created in the same content database.

Answer #6    Answered By: Dwight Becker     Answered On: Jul 30

That was exactly what I was looking for (and not seeing on
the App Management page).

Answer #7    Answered By: Amar Kumbar     Answered On: Jul 30

You may want to keep as few web  apps as possible but restrict how many
site collections  per content database.

Answer #8    Answered By: Marc Dixon     Answered On: Jul 30

I believe the recommended  limit from Microsoft is 50,000 top level sites, so it
doesn't sound like this would applicable to the original poster's situation.
Right now, I wouldn't fret too much about limitiing the number  of site
collections in a content database. Service Pack 1 adds native capabilities to
move sites into new content DB's as required. If you find that certain site
collections are growing at a rapid pace, you can move them into their own
database at any time. This is also a great method of defining site-specific
SLA's for your larger environments.

Didn't find what you were looking for? Find more on Recommended limit to # of site collections in a web app? Or get search suggestion and latest updates.