Skip to main content

Upgrade methods in SharePoint 2010

In SharePoint 2010 there are two upgrade methods available.
  • In-Place Upgrade
  • Database Attach Upgrade
Note: There is no Gradual Upgrade method available for upgrading SharePoint 2007 to SharePoint 2010.

There is also no direct upgrade method from SPS 2003 to SharePoint 2010. So if you want to upgrade from SPS 2003 to SharePoint 2010 you will have to upgrade SPS 2003 to MOSS 2007 and then from MOSS 2007 to ShaePoint 2010

Let us now have a look at both the available upgrade methods one by one

In-Place Upgrade
The InPlace upgrade is the easiest way to upgrade from MOSS 2007 to SharePoint 2010. In this approach you will install SharePoint 2010 on the same machine where MOSS 2007 was installed and the Upgrade wizzard will upgrade MOSS 2007 to SharePoint 2010. But make sure that you have run the pre-upgrade check before starting the upgrade to check all the pre-requisites are in place and all the errors are fixed.
Here are some of the features of InPlace Upgrade:
  • Very easy.. Wizard driven process. Click …Click ..finished
  • The Previous version is overwritten
  • All the sites are unavailable during upgrade
  • Site visitors continue to use the same URLs after the upgrade
Here are some of the advancements that Microsoft has done in the InPlace Upgrade method.
  • Restartable: In the previous versions of SharePoint this upgrade process was not restartable but in SharePoint 2010 you can restart the upgrade process
  • All Possible time-outs removed: In the previous versions if you used the Inplace upgrade a very big reason for the failure of upgrade was the time-out of one process or the other. Now all the possible time-outs have been removed to make this upgrade process more reliable
Here are the Pros/Cons of the In-Place Upgrade approach

Pros
  • Farmwide settings are preserved and upgraded.
  • Customizations are available in the environment after the upgrade
Cons
  • Servers and farms are offline while the upgrade is in progress
  • The upgrade proceeds continuously
  • After you begin an in-place upgrade, you cannot pause the upgrade or roll back to the previous version
Database Attach Upgrade
In database attach approach you install the SharePoint Server 2010 on a fresh Machine and you upgrade all the sites from your MOSS 2007 server by detaching the Content databases from MOSS Server and attaching them to the SharePoint 2010 server.
Here are some of the key features of Database Attach Upgrade method
  • SharePoint 2010 is installed on a fresh Server
  • You can upgrade the databases in any order
  • You can not upgrade any of the services or farm settings
  • You can upgrade several databases at the same time
  • Databases that can be Attached
    • Content DB
    • SSP DB
    • Project DB
  • Database that can not be attached
    • Configuration DB
    • Search DB
Pros/Cons of the Database Attach approach
Pros
  • You can upgrade multiple content databases at the same time, which results in faster upgrade times overall than an in-place upgrade
  • You can use a database attach upgrade to combine multiple farms into one farm
Cons
  • The server and farm settings are not upgraded. You must manually transfer settings that you want to preserve from the old farm to the new farm
  • Any customizations must also be transferred to the new farm manually. Any missing customizations may cause unintended losses of functionality or user experience issues
  • Copying databases over a network takes time and bandwidth
  • You need direct access to the database servers
Labels:

Comments

Post a Comment

Popular posts from this blog

How to get SPUser or SPGroup from Person or Group field

You have person or group field in SharePoint list and you want to programmatically get the user or person. The below code to gets SPUser from User or Group field in the list when multiple choice and Groups are not allowed in the field: //get SPUser SPFieldUser userField = (SPFieldUser)item.Fields.GetField("Users"); SPFieldUserValue userFieldValue = (SPFieldUserValue)userField.GetFieldValue(item["Users"].ToString()); SPUser user = userFieldValue.User; This part of code would help you to get SPUser when multiple choice is allowed and groups are not allowed: //Multiple choices are allowed SPFieldUser userField = (SPFieldUser)item.Fields.GetField("Users"); SPFieldUserValueCollection userFieldValueCollection = (SPFieldUserValueCollection)userField.GetFieldValue(item["Users"].ToString()); foreach (SPFieldUserValue userFieldValue in userFieldValueCollection) {     Console.WriteLine("     " + userFieldValue.User.LoginName); } And when group...
1 comment
Read more

SharePoint publishing page scheduling

In SharePoint 2010 publishing enabled team site collection is not showing schedule button in publish ribbon. Solution: Here is how to enable it  though the UI: Locate the SharePoint Server Web site on which you want to enable content approval and item scheduling. Click  Site Actions , click  Site Settings , and then click  Modify Pages Library Settings . Under  General Settings , click  Versioning Settings . Click  Yes  next to  Content Approval , and then click  OK . Click  Manage item scheduling .   Click to enable the  Enable scheduling of items in this list  check box, and then click  OK .
2 comments
Read more

Changing Content Type Hub URL

Change the Hub URL through powershell by using: Set-SPMetadataServiceApplication -Identity " " -HubURI " " For Ex: Set-SPMetadataServiceApplication -Identity "Managed Metadata Service" -HubURI "http://contenttype.Domain.Com" When you try to do this you get this rather scary message: This is SharePoint telling you that this is a major thing so be careful! Essentially all your content types that you have published out will be removed if they can, and you have to republish all of your content types out again which can cause some issue.
1 comment
Read more