move site collection to another new dedicate content database using powershell |

Опубликовано: 05 Октябрь 2024
на канале: Deviprasad Panda
197
0

We have to move site collection to dedicate content database when content database size growing too large. One content database present under a web application in SharePoint contains multiple site collections. We can create or add new content databases under web application when limit of maximum number of sites that can be created in this database exceed while creating new site collection. If one site collection present under a content database is growing large, user request to create a dedicate content database and move that particular site collection to another new content database. We need to follow the steps as described below to move site collection to dedicate content database.

Get site collection GUID using powershell
Get which content database site collection web application is stored
Create new content database in SharePoint
move site collection to different content database
IISRESET SharePoint server
Post Implementation testing

Before you move site collection to another content database, get guid of sharepoint site. You can get site collection guid using powershell script

Get which content database site collection web application is stored.
Get site collection content database details including web application, site url using the powershell command.

I described in detail about how to create or add a new content database in SharePoint in my previous post link https://sharepointtechnicalsupport.co...
Follow the post linked above for more details and use the powershell script for creating content database.

move site collection to different content database
Now we are ready to move site collections between databases using the powershell command Move-SPSite.

IISRESET SharePoint server
You will get a message in powershell window like "IIS must be restarted before this change will take effect. To restart IIS, open a command prompt window and type iisreset". You have to do IIS reset SharePoint server.

Post Implementation testing
After move site collection to new content database completed, you can check GUID of the site collection again. Its same as source location.
check content database of site collection to cross check the new content database as destination location.

Author : Deviprasad Panda
Contact me : https://sharepointtechnicalsupport.co...
Linkedin :   / deviprasadpanda  
My Blog : https://SharePointTechnicalSupport.com/
Website Post : https://sharepointtechnicalsupport.co...