PowerShell Cmdlets to Upgrade Content Databases from SP 2010 to 2013

By

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:
    •
Get-help *SPContentDatabase
  • 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.
Courtesy: Juan Carlos

Comments

Post a Comment

Popular posts from this blog

SharePoint logs and IIS logs backup/archive and Compress to a file

By
The data keeps on growing as the SharePoint Farm being adopted more into the company and customers. It brings more challenges in terms of keeping up with the pace of requests and data administration. We are going to address today one part of that problem which is managing SharePoint LOGS weather it is ULS, Diagnostic and Analytic logging. Also it includes IIS logs. To address this challenge I did wrote a small script to migrate these logs to a different directory and them zip these logs and move to a network storage or to another directory on the local hard drive. Some of the challenges to achieve this were ·         There are IIS logs with same file names in different directories (mainly IIS logs) we need to maintain the directories structure to not miss any logs. ·         The criteria to move these logs out is based on a number of day , like I need to move all the logs 15 or older away from the default logs folder or drive. ·         Then zip these logs and add to sa
Read more

Can you move a single large site collection into multiple content databases?

By
Although single content databases of upto 200GB is possible in Sharepoint 2010, administering and managing such a db would be a nightmare. What would you suggest for options in a case where there is one site collection and one corresponding content database. Can you have more than one content db for that one site collection? Can you expand the table to be hosted on other sql servers/machines? Does RBS help? Expert Comments: Officially there is support up to 4TBs with optimization, but realistically that is difficult to support and should only be used in extreme exceptions. Technically there were no real changes made to support the additional sizes, it was just an update to guidance. I still try and work with my customers to maintain databases no larger than 75-100GBs unless absolutely necessary. I do have customers with multi-terabyte farms. A single site collection can only use 1 Content DB. It is possible though to create solutions that use a single site collection that
Read more