Setup SharePoint My Sites via Managed Path in own content DB

CommunityEventsSharePointTechnology

Consider the following scenario:

You have an intranet web application named: ‘http://mywebapp’ it has it’s own Content Database named “MyWebApp_Content”.

You want to setup and configure My Sites to be used via the URL ‘http://mywebapp/mysites’ and you want all your My Sites content to be stored in it’s own new Content database named “MySites_Content”

Essentially this is using one web application with two content databases. Zac has this covered earlier in his post “Multiple Content databases which is the default” on how he has moved sites to two databases in WSS. My post also follows the same principal.

Chris Johnson (CJ) has this covered in his post “Moving your MySite location in MOSS” but hasn’t got details on how to get this working with a separate content database.

Following steps outline how to configure your existing web app ‘http://mywebapp’ to host ‘My Sites’ to be stored in a separate database

  • Go to “Application Management” and select “Content Databases” under “SharePoint Web Application Management”

  • Select the ‘http://mywebapp’ web application. And select “Add Content Database”

  • Create a new DB and name it: “MySites_Content” Once this DB is created select the existing database named: MyWebApp_Content. In the “Manage Content Database Settings” for ‘MyWebApp_Content’ select Database status to “Offline”

This will ensure that no new site collections are created in the default content database ‘MyWebApp_Content’. Taking this content database offline only prevents new site collections from being created. Users are still able to create sub sites and items and use the existing sites

](https://www.chandima.net/Blog/Lists/Posts/Attachments/138/TakeDBOffline.jpg)

Now you should be able to use ‘http://mywebapp/mysite’ and see your My Sites under the same URL and all content related your my sites will be in your new ‘MySites_Content’ content database.

← Back to blog