Posted by Patrick Boom on May 6, 2010
This week, we got one of our customized applications from SharePoint 2007 to work on a SharePoint 2010 machine. As as described in my previous post this does not go without problems. We tried the content database move method, meaning we made a backup of one of our 2007 content databases and restored that database on the 2010 SQL server.
We then attached the database to the SharePoint 2010 farm by using the following command:
stsadm -o addcontentdb -url http://sp2010 -databasename SP2007_Content_DB -preserveolduserexperience true
This command will initiate an upgrade of the database. Once upgraded, the sites are accessible from SharePoint 2010. There are a couple of things we noticed when we restored sites this way.
1. We can upgrade their look and feel using the Visual Upgrade settings from the site settings menu. This will however overwrite any custom look and feel you might have enabled for your site.
2. Document libraries that came out of the box in the 2007 site will easily migrate to 2010, including all its features, like multiple select and the ribbon interaction. However, custom document libraries based on their own shema.xml, will continue to have the 2007 functionality, even if visually upgraded. So the multiple select, ribbon interaction and so on will not work in these libraries. They are usable though, but not with all 2010 features.
Prior to this exercise, we needed to make sure all necessary code and customizations were installed on the system. But our solution that created our own look and feel (like custom master pages and stylesheets) really messed up the entire environment. I would enable alright, but your site would be crippled. Worst thing though, it would not reset to its original setting, meaning our site was dead in the water. So be very carefull when upgrading to 2010 with visual elements like master pages and layouts.
Posted in SharePoint 2007, SharePoint 2010 | Tagged: Database, Migration, Restore, Upgrade | Leave a Comment »
Posted by Patrick Boom on April 22, 2010
With Microsoft SharePoint 2010 approaching for official release on May 12th 2010 (earlier for MSDN, SA, VL licenses), businesses are already looking at how we can easily migrate to 2010.
So is it just click and install? Or are any special arrangements needed? Yesterday, we tested one of our custom extension packs on the new platform (RC).
There is some good news and some bad news😉 The good news is that features contained in the WSP pack were installed without a problem. The bad news is that some of the features in the pack introduced problems when activated.
Basically, all standard features, like content types, document libraries, list definitions and site definitions worked without a problem. Also the eventhandlers attached were also correctly attached in 2010.
So far so good. Features that were dependant on the 12 hive (for whatever reason, it is obviously not good practice) have a problem as the 12 hive is now called 14😉
The features that did not work upon install were those that were dependant or interacted with Shared Service Provider components. As the architecture behind these are complete different in SharePoint 2010, I did not expected it to work without a fight anyway🙂 The move to Service Applications, where the individual components of the Shared Service Provider were disconnected and isolated, caused several of my features to fail, as they could not find the Shared Service Provider. Also, some of the classes used for UserProfiles are now deprecated and replaced.
Another thing I noticed was that when I created a document library from my installed doc lib definition, it would be created, but function like the 2007 version. The row selection, checkboxes and 2010 look and feel were not available, meaning that the xml definition also needs an upgrade if you fully want to utilize the 2010 functions.
In short, some actions are indeed needed, before one could easily move to 2010. For standard sites though, that do not contain any drastic customizations, it is failry easy, using the content database attach method.
Nice day everone!
Posted in SharePoint 2007, SharePoint 2010 | Tagged: Migration, SharePoint 2007, SharePoint 2010 | 2 Comments »