Read time 9 minutes
A SharePoint site collection encompasses all your sites, lists, content, and templates, constituting a pivotal component of your SharePoint ecosystem. Nevertheless, there are specific scenarios that may necessitate the migration of your site collection from one content database to another. For example, if a site collection exceeds the capacity of its current content database, relocating it to a more spacious content database becomes imperative. Additionally, consolidating multiple small site collections from various content databases into a single content database can streamline administration and enhance efficiency.
This article will explore the process of transferring a site collection from one database to another using PowerShell commands. Additionally, we offer an alternative method for migrating a SharePoint site collection between content databases.
Before beginning the migration, make sure that the following conditions are true:
Additionally, it’s vital to assess the source site collection’s size since the auditing data is transferred when relocating the site collection. In cases of substantial auditing data, PowerShell can be employed to archive and reduce the audit data.
To find the size of a site collection, run the below command in SharePoint Management Shell:
$used = (Get-SPSiteAdministration -Identity <http://ServerName/Sites/SiteName>).DiskUsed
Also, make sure that the destination content database has enough space to accommodate the source site collection. It is recommended to have a free space three times the size of the site collection.
To move the site collection, you need to use the Move-SPSite command in PowerShell. Using this command, you can move a single site collection as well as multiple site collections to a new content database.
To move a single SharePoint site collection, you need to have the following memberships – securityadmin fixed server role, db_owner fixed database role, and the administrator group.
You need to have the same memberships as mentioned above to move multiple site collections from one content database to another.
By employing these commands, the seamless transfer of a site collection from one content database to another becomes a straightforward task. Nevertheless, an alternative approach for migrating a site collection from one server to another involves utilizing the backup and restoration process of the SharePoint site collection.
To safeguard your data, it’s essential to backup SharePoint Site collection using PowerShell. Subsequently, you can employ the same PowerShell technique to restore the Site Collection to SharePoint Server. Nevertheless, if you wish to relocate site collections from one content database to another effortlessly, consider utilizing Move-SPSite, as described earlier.
The SharePoint Migration tool, known as Kernel SharePoint Migrator, simplifies the process of migrating between different SharePoint versions. This utility boasts intelligent functionalities that facilitate the seamless migration of site collections between content databases. Whether you need to migrate a single site collection or multiple ones simultaneously, this tool ensures a glitch-free experience. It offers specialized features such as permission migration, selective migration, and migration scheduling. Moreover, you can utilize this utility to transfer data from the File System to SharePoint Server and OneDrive. Its straightforward workflow makes SharePoint Migration effortless, even for non-technical users.
That’s how you can easily migrate SharePoint Site Collection from one server to another with the help of Kernel SharePoint Migrator.
As site collections expand in size or when there’s a need to consolidate multiple site collections, the migration of site collections between databases becomes imperative. In this context, we will explore the process of transferring a SharePoint Server Site Collection from one content database to another using PowerShell commands. Additionally, we will introduce an advantageous tool called Kernel Migrator for SharePoint designed to facilitate the seamless migration of site collections between content databases.