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

For growth and performance reasons, I need to distribute my Webs across several Site Collections.

Still, I want the URL of these Webs to appear as though they are in the same place. Here is an illustration.

I want:

  • hxxp://sharepoint/mywebapp/customer1234
  • hxxp://sharepoint/mywebapp/customer4324
  • hxxp://sharepoint/mywebapp/customer5675
  • hxxp://sharepoint/mywebapp/customer6535

I DON'T want:

  • hxxp://sharepoint/mywebapp/sc4/customer1234
  • hxxp://sharepoint/mywebapp/sc4/customer4324
  • hxxp://sharepoint/mywebapp/sc5/customer5675
  • hxxp://sharepoint/mywebapp/sc5/customer6535


Is this possible? Any ideas?


share|improve this question

Defines a managed path for each customer, and create a site collection at each of this managed paths.

You will have to declare explicit managed paths for each customer.

Instead of /sites/*, you will have /SC1, /sc2, etc.

share|improve this answer
Thanks Steve, but I guess I was not clear enough in my description. I want, say, customer1 and customer3 in the same Site Collection, and customer2 and customer4 in another Site Collection, but I want the URL of them all to look like this: •hxxp://sharepoint/mywebapp/customer1 •hxxp://sharepoint/mywebapp/customer3 •hxxp://sharepoint/mywebapp/customer2 •hxxp://sharepoint/mywebapp/customer4 Any ideas? – Raoden Jun 13 '12 at 10:08
can't you create one site collection per customer ? it will be far more easier to maintain – Steve B Jun 13 '12 at 10:16
This is, honestly, my personal opinion too, but our customer, who will be hosting this solution, thinks that 20.000+ customer Site Collections is too much for them to administrate. I am not an admin, but a developer, so I'm not quite sure what to make of that... – Raoden Jun 13 '12 at 10:53
What about creating one site collection per customer, but putting them in a set of content database ? You can move sites from one content db to another later if you need – Steve B Jun 13 '12 at 11:03
This is exactly what the customer does not want to have to do; move around on 20.000 Site Collections, one by one – Raoden Jun 13 '12 at 11:10

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.