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

I wonder If there is any case we can have a site collection within another site collection in sharepoint 2007 and if we can have then whats the advantage and if we cant do it then why not.

share|improve this question
up vote 1 down vote accepted

You can have multiple site collections within a single web application.

A single site collection can contain 'n' number of subsites within itself.

Since SharePoint supports creating multiple subsites within any number of levels, each subsite virtually acts as a site collection (collection of subsites with any templates and at any levels) which is completely exportable and importable through command line(stsadm).

Essentially, any subsite that contains multiple subsites within itself is "almost" as good as a site collection expect for a few unique things that a top site collection gets url managed paths, alternate accessing mappings,collection administrators etc.

So to answer the question having a site collection within another site collection was only logical if SharePoint did not provide us with the option of creating a hierarchal arrangement of sites to any level while making them non exportable at the same time.

share|improve this answer

The answer depends on what you mean by having a site collection within another site collection.

The main purpose of site collections are they are completely separate, which be definition means that one cannot be inside another.

BUT thats from SharePoints point of view. You can set up managed paths such that you can create site collections which from an user point of view looks like they are within each other.

It very common to have a setup with the following urls to site collections:

  • http://intranet
  • http://intranet/sales
  • http://intranet/RD
  • http://intranet/HR
  • http://intranet/departmentX

From an user point of view it seems as if the department site collection are within the root site collection. But they are really completely separate.

The advantage of separate site collection are mainly security and the possibility to put them into separate content databases.

share|improve this answer
very good explanation, I was confused with "intranet"; as a root sitecollection but i guess we can add managed path e.g. "intranet/allsitecollectionsroot"; and then create site collections on top of them like "intranet/allsitecollectionsroot/sitecollection1"; – Muhammad Raja Jul 16 '12 at 12:19
When you create managed paths you have two options. A managed path can be wildcard like sites which means you can create site collection one level below it, or it can be explicit like the departments in my example, which means you can create site collection at that exact url. – Per Jakobsen Jul 16 '12 at 12:29
+ 1, I think Per nailed it really well :) – Falak Mahmood Jul 16 '12 at 12:34

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.