Wednesday, 6 February 2013

Moving Site Collection between Content Databases in SharePoint 2010

Moving Site Collection to another Content Database in SharePoint  2010

We had a requirement to have the existing site collection to be moved to a new dedicated content database for various reasons in a test environment.

Before performing this check the:
  • Site Collection Size
  • Disk Space free on the Database server
  • Whether Audit data needs to be moved
  • Solutions in use on this Site Collection 
  • Backup of the Existing Content - just in case something goes wrong but this task is fairly simple it depends on the importance of the site collection.

 Here are the steps performed to accomplish this on the test environment:

1)     Create a New Content Database

Syntax: New-SPContentDatabase -Name <ContentDbName> -WebApplication <WebApplicationName>

Example: New-SPContentDatabase -Name WSS_Content_ProjectCentre -WebApplication ‘ContosoWeb’

2)    Move the Site Collection to a new content database

Example: Move-SPSite -DestinationDatabase WSS_Content_ProjectCentre

Note: This doesn’t move the audit data if you have this in use, you have to use the other PowersShell commands please refer to the technet article.

3)     Run IISRESET to see the changes in Central Admin

4)     To Validate this:

Get-SPSite -ContentDatabase WSS_Content_ProjectCentre


  1. If you want your ex-girlfriend or ex-boyfriend to come crawling back to you on their knees (even if they're dating somebody else now) you must watch this video
    right away...

    (VIDEO) Text Your Ex Back?

  2. BlueHost is ultimately one of the best website hosting provider for any hosting plans you require.