By: Neil Barkhina
The task of upgrading SharePoint 2007 RTM to SharePoint 2010 involves a number of tasks. The main thing to be aware of is in order for your SharePoint 2007 environment to be a candidate for upgrade to 2010, it needs to at least be Service Pack 2 (or content database version 18.104.22.16821). In our staging environment, we ran into a situation where the server wasn’t upgrading to SP2 and was constantly throwing errors. So what we did was upgrade the content database using an in between staging environment which had SharePoint 2007 SP2 already installed and then moved that database to 2010. Here is a breakout of the steps you would need to take:
1. Backup the SharePoint 2007 RTM Content database. You can do this from SQL Management studio (if you don’t know which content database is the correct one, go into central administration and click on manage content databases and point to the correct web application). If this is a production environment you will want to put a Site Collection Lock of read-only on the site so that users stop uploading content to the environment. If the content database is large (10 GB or more) the backup will take a while so just be patient:
2. Restore the backup onto a new database, make sure the SQL version is the same or higher or else it will say the MDF headers are not the same.
3. Create a new web application on the SharePoint 2007 SP2 Server. We will use this web app to do the upgrade to SP2. Then go to manage content databases and remove the database associated with the new web application.
4. Run stsadm –o addcontentdb on the SharePoint 2007 SP2 server and point to the new database and the web application you just created.
5. Now the Content database should be upgraded. Do another backup of the newly upgraded database and move it to your SharePoint 2010 environment.
6. Restore the backup onto the SQL Server powering your SharePoint 2010 environment.
7. In SharePoint 2010 it’s the same procedure. Create a new web application and remove the content database. Then you will also run the stsadm –o addcontentdbcommand. The only different is there is a parameter that you can pass if you want to also do the “visual upgrade” as part of the database upgrade (we will get to that below). In my case I chose to leave the current SharePoint 2007 theme, which is the default. Another nice touch about the 2010 stsadm command is it gives you a percentage indicator as it’s performing the upgrade:
8. Now you should be able to hit the site, the old look and feel should still be in place:
9. If you want toupgrade to the SharePoint 2010 v4.master and look and feel, you will need to do a Visual Upgrade. You will find this under the Site Actions menu. Once you perform the visual upgrade you should have the new look and feel:
By: Neil Barkhina