• Article

Database-attach core upgrade to Project Server 2010

 

Applies to: Project Server 2010

Topic Last Modified: 2011-08-05

Important

Upgrading from the Project Server 2010 public Beta to the Project Server 2010 released version is explicitly blocked and not supported. This restriction applies to both the in-place and database-attach upgrade methods.

When you upgrade from Microsoft Office Project Server 2007 to Project Server 2010 by using the database attach upgrade process, you upgrade only the content for your environment, and not the configuration settings. Using the database attach upgrade process is useful when you are changing hardware or want to reconfigure your server farm topology as part of the upgrade process. It is also required if you are upgrading from Office Project Server 2007 deployed on a hardware that only supports a 32-bit server operating system.

Database-attach upgrade to Project Server 2010 can be done either one of two ways:

  • Database Attach full upgrade: Migrates the project data stored in the Office Project Server 2007 databases, plus the Microsoft Project Web App (PWA) site data stored in a SharePoint content database.

  • Database Attach core upgrade: Migrates only the project data stored in the Office Project Server 2007 databases.

This article provides the procedures required to perform a database attach core upgrade. For information about different types of methods for upgrading to Project Server 2010, see Project Server 2010 upgrade overview.

Process overview

When you perform a database attach core upgrade, you are basically using backup copies of your Office Project Server 2007 databases that contain your project data. You restore them on the Microsoft SQL Server instance that you are using for Project Server 2010, and then you upgrade the databases by creating a Microsoft Project Web App instance in Project Server 2010 that points to them. While both the database attach upgrade process and the in-place upgrade process are similar in functionality, the database attach upgrade keeps the original Office Project Server 2007 environment intact because you are using backup copies of the databases for the upgrade process.

Before you begin

Before you begin the database attach full upgrade to Office Project Server 2007, review the following information about permissions, hardware requirements, and software requirements. Follow the specified steps to install or configure prerequisite software or to modify settings.

Review required permissions

You must have at least the following permissions to complete the procedures in this article:

  • On the database server from which the databases are being detached you must be a member of the following roles:

    • The db_owner fixed database role.

    • The db_backupoperator fixed database role.

  • On the server farm to which the databases are being attached, you must be a member of the local Administrators group, and you must be a member of the following roles on the database server:

    • The dbcreator fixed server role.

    • The db_owner fixed database role.

  • In some environments, you must coordinate the move procedures with the database administrator. Be sure to follow any applicable policies and guidelines for handling databases.

Review required hardware and software

You must be running one of the following products on the database servers to perform these procedures:

  • On your Office Project Server 2007 environment: the Microsoft SQL Server Client tools for SQL Server 2000, SQL Server 2005, or SQL Server 2008. These are required to back up your required databases.

  • On your Project Server 2010 environment: a 64-bit version of one of the following products:

    • SQL Server 2008 Service Pack 1 with Cumulative Update 2

    • SQL Server 2005 Service Pack 3 with Cumulative Update 3

Note

Project Server 2010 databases can only be hosted on 64-bit versions of these two versions of SQL Server.

Perform prerequisite steps

Before you back up the databases, you must prepare for the upgrade by following these steps:

  1. Create a new server farm environment. For information about creating the new environment, see Deploy Project Server 2010 to a server farm environment.

  2. If you have custom site definitions in the old environment, create new site definitions and upgrade definition files for these site definitions and deploy them to the new environment.

Database attach core upgrade overview

A database attach core upgrade will upgrade your Office Project Server 2007 databases:

  • Draft

  • Archive

  • Publish

  • Reporting

The difference between a database attach core upgrade and a database attach full upgrade is that a full upgrade will upgrade not only your Office Project Server 2007 databases, but also your Project Web Access site data contained in a SharePoint content database. If you only want to upgrade your Project Web Access site data plus your Office Project Server 2007 project data, see Database-attach core upgrade to Project Server 2010.

To perform a database attach core upgrade, you must follow these general steps:

  1. Verify your Project Server 2007 data

  2. Back up the databases in SQL Server

  3. Restore the backup copies to the new farm

  4. Provision a new Project Server 2010 PWA instance using the restored databases

  5. Diagnose failures

  6. Configure for post-installation

  7. Verify whether the migration has been successful

These steps require that you have Project Server 2010 installed in your environment. You will not need to configure a Project Web App site prior to doing this procedure. You also do not need to do post-installation configuration such as configuring for Exchange Server integration or reporting, which can be done after upgrading. For more information about installing Project Server 2010, please see Deploy Project Server 2010 to a server farm environment.

Video demonstration

This video provides you an overview of how to use the database-attach core upgrade method to upgrade to Project Server 2010.

DB Attach Core Upgrade - Overview

Watch the video (https://go.microsoft.com/fwlink/p/?LinkId=217938). To download the video file, right-click the link, and then click Save Target As.

Verify your Project Server 2007 data

You must verify that your Office Project Server 2007 data is in a valid state to help ensure that your upgrade will be successful. You must verify the following:

  • All projects should be checked-in.

  • The Project Web App site name of "ProjectBICenter" is reserved in Project Server 2010. Verify that Office Project Server 2007 does not use this as a Project Web App site name.

  • The list name of "Project Detail Page" is reserved in Project Server 2010. Verify that Office Project Server 2007 Project Web App does not contain a list with this same name.

  • Resolve all custom field and lookup table name conflicts with names that are reserved in Project Server 2010. See the Custom field and lookup table name conflicts section for more information.

Custom field and lookup table name conflicts

There are certain custom fields and lookup tables name that are reserved in both Office Project Server 2007 and Project Server 2010. If you are upgrading from Office Project Server 2007, verify that you do not have custom field names that are in conflict with the names reserved for Project Server 2010. If any of these names are used in the current Office Project Server 2007 database, the custom fields and outline codes must be changed in Office Project Server 2007 before proceeding further with the migration. Use Microsoft Office Project Professional 2007 connected to a Office Project Server 2007 instance to validate and take corrective action.

Reserved outline code names

Outline code name Type Office Project Server 2007 Project Server 2010

Cost Type

Resource

X

X

Health

Task

X

X

State

Project

X

X

Team Name

Resource

X

X

Department

X

Flag Status

X

Reserved custom field names

Custom field name Type Office Project Server 2007 Project Server 2010

Cost Type

Resource

X

X

Health

Task

X

X

State

Project

X

X

Team Name

Resource

X

X

Sample Approved Finish Date

Project

X

Sample Approved Start Data

Project

X

Sample Areas Impacted

Project

X

Sample Assumptions

Project

X

Sample Business Need

Project

X

Sample Compliance Proposal

Project

X

Flag Status

Task

X

Sample Goals

Project

X

Sample Post-Implementation Review Date

Project

X

Sample Post-Implementation Review Notes

Project

X

Sample Primary Objectives

Project

X

Project Departments

Project

X

Project Impact

Project

X

Sample Proposal Cost

Project

X

Sample Proposed Finish Date

Project

X

Sample Proposed Start Date

Project

X

Relative Importance

Project

X

Resource Departments

Resource

X

Video demonstration

This video provides you an overview of how to prepare your Office Project Server 2007 data for upgrade when you are using the database-attach core upgrade method to upgrade to Project Server 2010.

DB Attach Core Upgrade - Prepare for Upgrade

Watch this video (https://go.microsoft.com/fwlink/p/?LinkId=217939). To download the video file, right-click the link, and then click Save Target As.

Back up the databases in SQL Server

Follow the appropriate procedure to back up your Office Project Server 2007 databases in SQL Server 2000, SQL Server 2005, or SQL Server 2008 (depending on which you are using to host the databases). Repeat the procedure for each of the following databases in the original server farm:

  • Project Server_Draft

  • Project Server_Archived

  • Project Server_Published

  • Project Server_Reporting

At the end of this procedure, you will have created duplicates of each database.

To back up a database in SQL Server 2000

  1. On the database server, click Start, point to All Programs, point to Microsoft SQL Server, and then click Enterprise Manager.

  2. In SQL Server Enterprise Manager, expand Microsoft SQL Servers.

  3. Expand SQL Server Group.

  4. Expand (local) (Windows NT).

  5. Expand Databases.

  6. Right-click the database that you want to back up, point to All Tasks, and then click Backup Database.

  7. In the SQL Server Backup dialog box, in the Name box, specify a name for the backup, and then, in the Backup area, select Database - complete.

  8. In the Destination area, either select an existing destination or do the following:

    1. Click Add.

    2. In the Select Backup Destination box, select File Name, and then, next to the File Name box, click Browse.

    3. In the Backup Device Location - (local) dialog box, in the File name box, type a file name, and then click OK.

    4. Click OK again to close the Select Backup Destination dialog box.

  9. Click OK to start the backup process.

  10. Click OK to acknowledge that the backup process is complete.

Repeat the previous procedure to back up the remaining required databases.

To back up a database in SQL Server 2005

  1. On the database server, click Start, point to All Programs, point to Microsoft SQL Server 2005, and then click SQL Server Management Studio.

  2. In the Connect to Server box, fill in the connection information, and then click Connect.

  3. After you connect to the appropriate instance of the SQL Server 2005 Database Engine, in Object Explorer, expand the server tree by expanding the server name.

  4. Expand Databases, right-click the database that you want to back up, point to Tasks, and then click Back Up. The Back Up Database dialog box appears.

  5. In the Source area, in the Database box, verify the database name.

  6. In the Backup type box, select Full.

  7. Under Backup component, select Database.

  8. In the Backup set area, in the Name text box, either accept the default backup set name that is suggested or type a different name for the backup set.

  9. In the Destination area, specify the type of backup destination by selecting Disk or Tape, and then specify a destination. To create a different destination, click Add.

  10. Click OK to start the backup process.

Repeat the previous procedure to back up the remaining required databases.

To back up a database in SQL Server 2008

  1. On the database server, click Start, point to All Programs, point to Microsoft SQL Server 2008, and then click SQL Server Management Studio.

  2. In the Connect to Server box, fill in the connection information, and then click Connect.

  3. After you connect to the appropriate instance of the SQL Server 2008 Database Engine, in Object Explorer, expand the server name.

  4. Expand Databases, right-click the database that you want to back up, point to Tasks, and then click Back Up. The Back Up Database dialog box appears.

  5. In the Source area, in the Database box, verify the database name.

  6. In the Backup type box, select Full.

  7. Under Backup component, select Database.

  8. In the Backup set area, in the Name box, either accept the default backup set name or type a new name.

  9. In the Destination section, specify the type of backup destination by selecting Disk or Tape, and then specify a destination. To create a different destination, click Add.

  10. Click OK to start the backup process.

If you need more information about backing up databases in SQL Server, see the following articles:

Video demonstration

This video describes how to create backup files of Office Project Server 2007 databases when you are using the database-attach core upgrade method to upgrade to Project Server 2010.

DB Attach Core Upgrade - Backup databases

Watch this video (https://go.microsoft.com/fwlink/p/?LinkId=217940). To download the video file, right-click the link, and then click Save Target As.

Restore the backup copies to the new farm

After you have configured the new Project Server 2010 server farm, you can restore the backup copies of the databases on the SQL Server instance that you are using to host your Project Server 2010 databases. Note that you must restore to a 64-bit version of SQL Server 2008 SP1 with CU2, or 64-bit SQL Server 2005 SP3 with CU3. Start with one database, and then verify that the recovery has worked before you restore the other databases.

The following section provides procedures for restoring the backups.

To restore a backup copy of a database in SQL Server 2005 Enterprise Edition

  1. In SQL Server Management Studio, right-click Databases, and then click Restore Database. The Restore Database dialog box appears.

  2. In the Restore Database dialog box, on the General page, in the To database box, type the name of the database you are restoring.

  3. In the To a point in time box, keep the default (Most recent possible).

  4. To specify the source and location of the backup sets to restore, click From device, and then click Browse to select the backup file.

  5. In the Specify Backup dialog box, in the Backup media box, be sure that File is selected.

  6. In the Backup location area, click Add.

  7. In the Locate Backup File dialog box, select the file that you want to restore, and then click OK.

  8. In the Select the backup sets to restore grid, select the Restore check box next to the most recent full backup.

  9. In the Restore Database dialog box, on the Options page, under Restore options, select the Overwrite the existing database check box.

  10. Click OK to start the recovery process.

Repeat the previous procedure to restore the remaining required databases.

To restore a backup copy of a database in SQL Server 2008 Enterprise

  1. After you connect to the appropriate instance of the SQL Server 2008 Database Engine, in Object Explorer, expand the server name.

  2. Right-click Databases, and then click Restore Database. The Restore Database dialog box appears.

  3. In the Restore Database dialog box, on the General page, type the name of the database to be restored in the To database list.

  4. In the To a point in time box, retain the default (Most recent possible).

  5. To specify the source and location of the backup sets to restore, click From device, and then click Browse to select the backup file.

  6. In the Specify Backup dialog box, in the Backup media box, be sure that File is selected.

  7. In the Backup location area, click Add.

  8. In the Locate Backup File dialog box, select the file that you want to restore, click OK, and then, in the Specify Backup dialog box, click OK.

  9. In the Restore Database dialog box, under Select the backup sets to restore grid, select the Restore check box next to the most recent full backup.

  10. In the Restore Database dialog box, on the Options page, under Restore options, select the Overwrite the existing database check box.

  11. Click OK to start the recovery process.

Repeat the previous procedure to restore the remaining required databases.

For more information about restoring databases in SQL Server, see the following articles:

Video demonstration

This video describes how to restore Office Project Server 2007 databases on the database server that is hosting the Project Server 2010 installation when you are using the database-attach core upgrade method to upgrade to Project Server 2010.

DB Attach Core Upgrade - Restore Databases

Watch this video (https://go.microsoft.com/fwlink/p/?LinkId=217941). To download the video file, right-click the link, and then click Save Target As.

Provision a new Project Server 2010 PWA instance using the restored databases

In Project Server 2010, you can now create a Project Web App instance using the Office Project Server 2007 databases you restored to SQL Server in the previous step. When the instance is created, the restored databases will be upgraded to Project Server 2010.

Create a Project Server 2010 PWA instance using the restored Office Project Server 2007 databases

  1. On the SharePoint Central Administration Web site, in the Application Management section, click Manage service applications.

  2. On the Manage Service Applications page, click Project Server Service Application.

  3. On the toolbar, click Manage.

  4. On the Manage Project Web App Sites page, click Create Project Web App Site.

  5. On the Create Project Web App Site page:

    1. In the Project Web App Site Location and Administrator Account fields, keep the default values.

    2. In the Primary Database field, type the name of the database server where your restored Office Project Server 2007 databases are located.

    3. Verify that the names of the Project Server databases match the names of the restored Office Project Server 2007 databases that you will use. If they do not, change them so that they match.

      Important

      The databases names must be exact matches with the restored Office Project Server 2007 database names in SQL Server. If the names do not match, a new Project Server 2010 database will be created and the restored Office Project Server 2007 database will not be upgraded.

    4. Click OK.

Project Server will start the PWA site creation process. Click Refresh occasionally to view the status of the instance provisioning. Be patient as this occurs, as it may take a while to finish. When the site creation process has finished, the status shown on the PWA site list is Provisioned.

The URL can now be used to connect Internet Explorer, the Project client, and custom-code based clients to Project Web App.

Note

The first invocation of the Internet Information Services (IIS) application pool that contains the Project Web App application can be slow as the .NET Framework application is loaded and compiled.

Video demonstration

This video describes how to provision a new Project Web App instance that uses your restored Office Project Server 2007 databases when you are using the database-attach core upgrade method to upgrade to Project Server 2010.

DB Attach Core Upgrade - Provision Instance

Watch this video (https://go.microsoft.com/fwlink/p/?LinkId=217943). To download the video file, right-click the link, and then click Save Target As.

Diagnose failures

If your Project Web App instance does not provision successfully, the provision process will return a status of Failed, at which point you can check the upgrade logs for additional details about the failure.

The upgrade log is located in the following default location: %PROGRAMFILES%\Common Files\Microsoft Shared\Web Server Extensions\14\Logs

Each upgrade attempt creates a new log, so view the most current logs. You can view the correct log file by noting the Date/Time stamp that is embedded in the log file name (for example, Upgrade<DateTime>.LOG). Open the log files in Microsoft Excel and search for “Failure” to find more information about the why the upgrade failed. For example, the log file may describe the failure occurring because of an invalid custom field name in the data. You would then need to return to Office Project Server 2007 and fix the issue (possibly by renaming the custom field). You would then need to run through the steps in this procedure again (back up and restore the databases, and then create a new instance in Project Server 2010).

If the upgrade log does not give you any insight in correcting the problem, contact Microsoft Support Services.

Configure for post-installation

After creating the Project Web App instance to upgrade your Office Project Server 2007 databases to Project Server 2010, you can do additional post-installation steps to make the deployment more functional. For example, additional post-installation configuration steps include:

  • Configure reporting for Project Server 2010

  • Configure Excel Services in Microsoft Office SharePoint Server 2007

  • Configure single sign-on

  • Configure the cube building service

  • Configure Time Reporting periods

  • Configure Exchange integration

For more information about these steps, see Install and configure Project Server 2010.

Verify whether the migration has been successful

Open Project Web App and check whether your data has migrated properly. Run your regular testing on this server. If you notice any differences from normal behavior, document this and contact Project Server 2010 Support Services.