Performing Upgrade through Database Attach SharePoint 2010


The database approach is followed when the existing server does not meet the hardware and software requirements for SharePoint installation to do an Inplace Upgrade. In such a case SharePoint is installed on a new server and the content from the existing server is attached to the new server. I will be explaining how a MOSS 2007 web application can be upgraded using this method. To do the migration your MOSS installation has to be MOSS SP2 or later. If not upgrade it to SP2 or later.
To do a database attach first you have to detach the database from the MOSS installation. This should be done to avoid any inconsistencies in data that may be caused due to updates to the content databases during the upgrade process. To do this

  1. Open SQL Server Management Studio
  2. Right click on the content database you want to detach, point to Tasks and click on Detach on the pop out. 


Then take back up of the content database you have detached. To do this, right click on the database in SQL Server Management Studio. In the Tasks menu, click Back Up. 
The next step is to restore from this back up. Copy the backup file to the new server. Right click on databases in the SQL Server Management Studio and click Restore Database. Give a name to the new database. Select “From Device” in the “Source for restore” and select the backup file. Select the database in the list of backup sets and click Ok. This will restore the database. Then give “db_owner” rights to the SharePoint service account and to the person who is intended to do the database attach if you are not the one to do that.
Click OK.
Create a web application in SharePoint from the central administration. Go to manage content databases and delete the database created for that web application. Before you delete the database observe that the number of site collections in the dataset is zero. Then attach the restored database to the application. To do that,
Open SharePoint power shell and give the following command.
 
Mount-SPContentDatabase -Name <DatabaseName> -DatabaseServer <ServerName> -WebApplication <URL>

This command will upgrade the database and give the report in a text file.

If you have multiple site collections in the application being migrated, see that you attach the content database having the root site first before any other database.
Go to Manage content databases in the central admin and make sure you have the restored database attached to the web application and the number of site collections is not zero.
In my source application I have one site collection so it is showing a one in the Current number of site collections
Open the site in the browser and you should be able to see your site with a new user interface of SharePoint 2010.
This is how my site in MOSS 2007 looked like


(I have joined to screen shots in one pic to show the entire page)
This is how it looks in SharePoint 2010.
(I have joined to screen shots in one pic to show the entire page)
 
If your MOSS application has any custom web parts defined, you have to rebuild them on 64-bit machines if necessary and move the DLLs to the new server. Also you have to move the user controls from the 12 hive and place them in 14 hive of the new server. You also have to make changes to the web.config of application on the new server and register them as safe controls.

Comments

  1. ologunobaFebruary 13, 2012 at 11:51 AM

    Nice post, but my prdicament is sligtly diffent, the issue with MOSS 2007 deploymet is not with the hardware, but rather with the initial configuration. A single Farm, a singe Web application and a single Content database wa deployed. Right now due to the need to implement proper information architecture and because of issues with managing our almost 2 TB of data, it is required to seperate every department into seperate content databases.
    Can migration by database attach be used to do this.
    Note i am currently running MOSS 2007 and intend to migrate to sharepoint 2010

    ReplyDelete

Post a Comment

Popular posts from this blog

Create a Custom Timer Job in SharePoint 2010

Image
I had to create a custom timer job in SharePoint 2010 recently, but could not find a blog which explained the complete procedure to do this. So I decided to write one. In this post I will give a step by step process to create a Custom timer job in SharePoint 2010 using Visual Studio 2010. Timer jobs are created by extending the SPJobDefinition class and deployed as features. So we will create a class which extends the SPJobDefinition class. Then we will create a feature and we will handle the featureActivated() event of that feature. In that we will instantiate the class created. Let us see how to do all this. Create an empty SharePoint project in VS 2010. Give the Site Collection URL where you want this feature will be activated. Create a class in the project.   Add these namespaces using Microsoft.SharePoint; using Microsoft.SharePoint.Administration; class MyTimerJob : SPJobDefinition { public MyTimerJob() : base () { } public MyTimerJob( SPWebApplic
Read more

Create web part pages with custom layouts in SharePoint 2010

Image
SharePoint provides web part pages with eight layouts by default. Unfortunately the process of creating web part pages with custom layouts is a little complex. In this post i will show you how you can create web part pages with custom layouts. I have created a component which will deploy an application page which can be used to achieve this. Go to http://archive.msdn.microsoft.com/customspcf  and download the wsp file with the name CustomSPCF.wsp Deploy the solution. This will deploy an application page at /_layouts/customspcf/customspcf.aspx It will add four web part page layouts at 14\Template\1033\Sts\Doctemp\Smartpgs\CustomSPCF\ and four images corresponding to the layout at 14\Template\Images\CustomSPCF\ The below image shows how the application page will look like You can customize the application page and replace the deployed custom layouts or add new layouts. Follow the below steps to replace the exisitng layouts. 1. Go to the applciation page at 14\Templates\L
Read more

Config file for SharePoint custom timer jobs

Image
SharePoint timer jobs run under the OWSTIMER.exe process. This process has a configuration file associated with it. We can use this config file to specify the configuration settings that are to be used in custom timer jobs. Open the OWSTIMER.EXE.CONFIG and add the <appSettings> tag to it. Then add your key value pairs under this appSettings tag For this you have to add a reference to System.Configuration Then you can use the  System.Configuration. ConfigurationManager .AppSettings[ key ]  to retrieve the values for a key from the config file. Example:  string dept = System.Configuration. ConfigurationManager .AppSettings[ "Department" ];
Read more