I wanted to move a site collection to its own content DB and not have any other site collections added. This was for migration purposes but eventually the new content DB will be used for other sites.
The first step to create a new empty content database. Therefore from Central Admin, under Application Management, select Manage content databases in the Databases section:
On the Content Databases page, click on the Add a content database link:
Back on the Content Databases screen, click the link of the new content database you created. The Manage Content Database Settings page appears. Change the Database status to Offline:
This is such that nobody can add new site collections and have them stored in your new content database. Click OK.
Next, on the server, open SharePoint 2013 Management Shell and issue the following statement:
Move-SPSite <<http://server/sites/SiteCollection>> -DestinationDatabase <<NewContentDBName>>
The first step to create a new empty content database. Therefore from Central Admin, under Application Management, select Manage content databases in the Databases section:
On the Content Databases page, click on the Add a content database link:
On the New Content Database page, enter the new database name and click OK:
Back on the Content Databases screen, click the link of the new content database you created. The Manage Content Database Settings page appears. Change the Database status to Offline:
Next, on the server, open SharePoint 2013 Management Shell and issue the following statement:
Move-SPSite <<http://server/sites/SiteCollection>> -DestinationDatabase <<NewContentDBName>>
Run IISReset per the message.
Refresh your Content Databases screen and you should see 1 site collection in your new content database, and 1 less in the original content database:
No comments:
Post a Comment