In my previous article about upgrading from SharePoint 2010 to SharePoint 2013, I explained how to complete this task by using the Database Attach upgrade method. This technique implies the necessity to use some PowerShell cmdlets available in SharePoint 2013 to work with either content databases or service applications ones.
In this new article, I will summarize basic Powershell cmdelts we have available to upgrade SharePoint 2010 content databases to SharePoint 2013:
- Before going into detail, you can list available cmdlets by executing the following PowerShell sentence in the SharePoint 2013 Administration Console:
- After executing this sentence, you will have a list with all the cmdlets available:
- From this list, the cmdlets we are interested in are the following: Test-SPContentDatabse, Upgrade-SPContentDatabase and Mount-SPContentDatabase.
- Test-SPContentDatabase cmdlet allows you to identify any issue or customization you could take into account when upgrading a content database to SharePoint 2013: features installed in the SharePoint 2010 environment that should be in the SharePoint 2013 ones, language packs installed, etc. Below, you can find the general syntax for Test-SPContentDatabase.
Test-SPContentDatabase –Name <ContentDabaseName> -WebApplication <URL>
- If the command execution detects issues in the content database, it will appear in the output window. For instance, a common issue is to have orphan objects in the content database.
- Ugrade-SPContentDatabase cmdlet allows you to upgrade a content database that has some issues or upgrade it from one product build to another one. This command is used to only to resume a failed Upgrade. The syntax of this cmdlet is quite simple as you can see in the following script:
Upgrade-SPContentDatabase -Identity <ContentDabaseName>
- If you execute this command in the SharePoint 2013 Administration Console, you will have to confirm that you want to start the upgrade process in the related database. If there are no problems, a warning message will be shown indicating that the database doesn’t need to be upgraded.
- Finally, you have to execute the Mount–SPContentDatabase cmdlet in order to add a content database to an existing web application. Please note that only once you have fixed any existing problem found with the content database, should you execute this command. You are then ready to add to an existing web application. Mount-SPContentDatabase syntax is quite simple as you can see below:
Mount-SPContentDatabase -Name <ContentDatabaseName> -WebApplication <URL >
And that’s all there is to know about upgrading from basic PowerShell cmdlets to SharePoint 2010 content databases to a CloudShare SharePoint.