If you want to move from SharePoint 2007 to SharePoint 2010, you have to know that there are three main migration approaches:
- In-Place Upgrade which installs SharePoint 2010 on the same hardware where SharePoint 2007 is installed.
- Database attach upgrade to a new farm, which means you have to make a backup of your existing content databases and restore them on a SharePoint 2010 farm.
- Hybrid approaches in order to take advantage of the benefits provided by In-Place and database attach upgrade methods.
In this article I will show you how to upgrade a SharePoint 2007 content database to be used on a CloudShare SharePoint 2010 environment:
- In your CloudShare SharePoint 2010 environment, start SQL Server Management Studio, connect to your SQL Server instance on the server and restore the SharePoint 2007 content database backup by using the “Restore Database…” menu option available at the Databases folder. In the “Restore database” window specify the name of the database to be restored and the path where the backup is located. Click the “Ok” button in order to start the restore process.
- Once the content database is restored on the SQL Server instance, go to the SharePoint 2010 Central Administration and create a new Web Application. In my case, I have created a web application using the 90 port number.
- Before adding the restored content database to the web application, you must ensure the database is ready to be applied to a specific SharePoint 2010 web application. You have two approaches to achieve this:
- Use the Preupgradecheck STSADM operation which detects any issue or problem when trying to attach a content database to another SharePoint farm: missing features, language pack to be applied in the destination farm, etc.
- Execute the Test-SPContentDatabase cmdlet in the CloudShare SharePoint 2010 environment which allows to detect the same kind of issues Preupgradecheck does.
- In our case, we are going to use the Test-SPContentDatabase so we need to open the SharePoint 2010 Management Shell and type this command using the following syntax:
- If the command execution detects issues in the content database, you will see these in the output window. For instance, a common issue is to have orphan objects in the content database.
- If there are no issues when executing Test-SPContentDabase, you will not see an information message in the output window.
- Once you have fixed any problem found with the content database, you are ready to add to an existing web application. You can do it by executing the Mount-SPContentDatabase cmdlet using the following syntax:
- As a result, in the output window you will see the ID assigned to the content database in the CloudShare SharePoint 2010 environment, the web application assigned and the number of sites available.
- You can verify the result through the “Manage Content Databases” page available at the SharePoint 2010 Central Administration.
- Of course, you can also check what site collections have been added to the web application once the upgrade process has finished.
- As you can expect, any of these sites have a SharePoint 2007 look & feel in order to ensure the site is completely functional. Once you are sure the site works as expected, you can switch it to a SharePoint 2010 look & feel through the “Visual upgrade” option available in the “Site Actions” menu.
- Below is the look and feel of the SharePoint 2010 upgraded site.
And that’s how to upgrade SharePoint 2007 content databases to a CloudShare SharePoint 2010 environment using the database attach technique. Happy CloudSharing!
You may also be interested in reading about:
Sharepoint 2010 SQL server 2012