Project Server VME: Attach the Windows SharePoint Services 2.0 content database to the farm

 

Applies to: Project Server 2010

Topic Last Modified: 2013-12-18

Important

This step is optional and is only required if you are migrating Microsoft Office Project Server 2003 project workspace data.

Use the following procedure to attach the copy of the Windows SharePoint Services 2.0 content database to the Microsoft Office Project Server 2007 farm in the VME. Perform this procedure after you have restored the content database containing your project workspace data to the Project Server virtual migration environment (VME) virtual machine in Microsoft SQL Server 2005. Once attached, the project workspaces are migrated to Windows SharePoint Services 3.0.

Attaching your Windows SharePoint Services 2.0 content database to the farm in the VME is a step in the VME migration phase. For additional steps, see Project Server VME: Migration phase.

To attach the Windows SharePoint Services 2.0 content database to the VME farm

  1. Open a Command Prompt window and navigate to the location of Stsadm.exe. (The default location is <Drive>:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\bin.)

  2. Run the following Stsadm command to attach a copy of your Windows SharePoint Services 2.0 content database to Windows SharePoint Services 3.0 and upgrade it.

    stsadm.exe -o addcontentdb -url http://<server>:<port> -databasename <WSS v2.0 content database> -databaseserver <DB Server name>

    For example:

    stsadm.exe -o addcontentdb -url http://VME -databasename YourContentDBName databaseserver VME

  3. After running Stsadm.exe, you can track the progress of the upgrade by looking at upgrade.log in the ULS log directory. (The default location is C:\program files\common files\Microsoft shared\Web server extensions\12\logs\upgrade.log.) Upgrade has finished on a given content database when the following line is included in the log:

    [SPManager] [DEBUG] [<Date> <Time>]: Using cached [SPContentDatabase Name=<DB NAME> Parent=SPDatabaseServiceInstance] NeedsUpgrade value: False.

  4. If the upgrade process fails for any reason (as indicated in the log), the Windows SharePoint Services upgrade process can be restarted. To restart the upgrade process, run the command Stsadm.exe -o upgrade and look at the logs to view the progress. Upgrade has finished when the command prompt returns Operation completed successfully.

Note

For more information about how to migrate a content database to Windows SharePoint Services 3.0, see Attach databases and upgrade to SharePoint Foundation 2010.