All about SharePoint best practice... ask me how
Setup SharePoint My Sites via Managed Path in own content DB [ Posted on: 28-March-2008 ]

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

  1. Go to “Application Management” and select “Content Databases” under “SharePoint Web Application Management
  2. Select the ‘http://mywebapp’ web application. And select “Add Content Database
  3. Create a new DB and name it: "MySites_Content"
  4. Once this DB is created select the existing database named: MyWebApp_Content.
  5. 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

TakeDBOffline

  1. Go to Application Management and select “Define Managed Paths” under “SharePoint Web Application Management

    ManagedPath
  2. Select the 'http://mywebapp' web application and create a new path named ‘mysite’ and select “Explicit inclusion
  3. Create a another managed path named ‘personal’ and make it a “Wildcard inclusion
  4. Go to “Application Management” and select “Create Site Collection
  5. Ensure that the path selected is 'http://mywebapp/mysite' **(Important)**
  6. Name it ‘My site host’ and select the “My Site” template from the templates list from the “Enterprise” tab

    MySiteHost
  7. Go back to Central Administration and select the Shared Services Provider configuration
  8. Select “My Site Settings” and Set "Personal site provider" to "http://mywebapp/mysite/" and "Location" to "personal"

     SSPMySites
  9. Go back to Central Administration and enable “Self Service Site Creation” for the web application ‘http://mywebapp’

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.

Posted by Chandima Kulathilake | 7 Comments | Bookmark with:        
Tags: SharePoint 2007, Planning, Administration, Deployment

Comments and Feedback
Thursday, 8 May 2008 05:10 by Nicholas Hadlee
Hi Chandima, Have you ever come across the "There has been an error creating the personal site. Contact your site administrator for more information" or the hotfix that is supposed to fix it http://support.microsoft.com/kb/937207?
Sunday, 11 May 2008 09:36 by Chandima
@ Nicholas: Usually this is due to insufficient permissions on your database that contains your my sites data. Are you following my above steps to create my sites via the managed path? Specifically the mysites application pool account will need the [dbcreator] role in SQL Server. If you are using the application pool being set to Network Service you may encounter this error. Either way don't try to change the application pools on the fly. Start from the beginning.
Thursday, 22 May 2008 12:09 by Phill Jenkins
I notice your intructions don't say to take the original database back 'online'. Doesn't that mean that any future site collection created under http://mywebapp (not mysites) will end up in the MySites_Content database? How can you ensure that stuff created under mywebapp goes in mywebapp_content db and stuff created under mywebapp/mysites goes in mysites_content db?
Thursday, 22 May 2008 04:53 by Chandima
@ Phil Jenkins: The idea noted here was to prevent any new site collections being created in the "MyWebApp_Content" content DB. So the answer to your question is that you can't enforce site collections to be created in a particular DB when a site collection is created. Ideally you will create the number of top level site collections you need prior to taking the DB offline. The reasons you would want all "My Sites" in a separate DB is to have manageability over a large number of sites in this case My Sites.
Saturday, 14 Jun 2008 07:39 by Search the Web on Snap.com
It doesn't help me. the same process and service accounts i have for Dev, QA and Prod .Now i had configured My Site works in QA, but doesn't work in Dev. now am worried abt to prod to install and configure.
Wednesday, 18 Jun 2008 03:31 by Darrel
One thing to note is that My Sites requires 'self service site creation' turned on, so people can create their my site. Since that's a web-app level setting, you may or may not want that for your other portals in that web-app.
Tuesday, 30 Dec 2008 11:04 by Chris
I've followed these steps exactly but everytime a new "My Site" is created, it creates a new Site Collection nor does it place the site into the MySite_ContentDB.
Your Name: (Required)
Website URL:
Your Email:
(Will not be displayed)
Feedback and Comments: (Required)
Are you a person? Please enter the charachters in the box below.


 
View the privacy policy.

 
Tags
 
Affiliations
Microsoft MVP (Microsoft Office SharePoint Server)

MCTS - WSS/MOSS Configuration

CKS - Team Member Add to Technorati Favorites

View Chandima Kulathilake's profile on LinkedIn



Kindly hosted by:
Kindly hosted by Intergen





Chandima Kulathilake's Facebook profile