Microsoft Project 2010
The official blog of the Microsoft Project product team. Learn how to manage your work effectively
Common Tasks
recent posts
Tags
Office Blogs
Project Community Blogs
Office Blogs
Archives
Archives

Project Server Data Migration - Cheat Sheet

MSDN Blogs > Microsoft Project 2010 > Project Server Data Migration - Cheat Sheet

Project Server Data Migration - Cheat Sheet

15 Jun 2006 10:04 PM
  • Comments 30

Data Migration can be a long difficult progress. In Project 2007 we made a lot of investiments to make this process a lot smoother for users.

 

This post provides a list of quick steps to migrate your Project Server 2003 data into Project Server 2007. I've done it several times and it works well. If there are any failures, the log gives you detailed information for troubleshooting the issue.

 

This list doesn't provide a detailed documentation of the process or all the detailed steps or how to troubleshoot problems. For that, refer to the Beta 2 documentation.

 

1)    Install Project Server 2007 and provision a Project Web Access site

 

2)    Backup your clean Project databases (all 4 of them). If you run into problems you can restore the databases and start over

  

3)     Get your Project 2003 database ready. Restore an existing Project 2003 database onto the same SQL server as the Project Server 2007. Or create a linked server on the Project Server 2007 SQL Server (SQL Server instance->Security->Linked Servers). Link it to the Project Server 2003 SQL Server. In the security tab choose ‘be made with this security context’ and give a SQL Auth account (Eg. user: sa   password:<whatever>)

 

4)    Install Project 2007 Professional and choose the “install migration tool” advanced option in setup

 

5)    Change the default Migration ini file that gets installed with Project Professional (you can find it at \Program Files\Microsoft Office\Office12\ P12MIGRATION.INI.SAMPLE)  Add in the right values for Project Server 2003 databases, Project Server 2003 Linked SQL Server, Project Server 2007 PWA etc. ***Spend some time to make sure all your parameters are valid. There are detailed explanation of each parameter***

  

6)     Run the migration tool from the command line:   "<drive>:\Program Files\Microsoft Office\OFFICE12\p12migrationtool.exe" -c "<location>\p12migration.ini"

 

7)     Look at the command line/migration log to make sure everything is fine. If not, do corrections and re-run migration tool - it should start from where it stopped last.  If there is a irrecoverable problem, make changes in Project Server 2003, restore the clean Project Server 2007 databases and retry migration.

 

8)     If you have any local windows accounts (eg. <Machine\Brad Sutton>), make sure you use PWA->edit user functionality to edit those accounts so that they are valid.

 

9)     Go to the migrated PWA site as an admin, edit each migrated security category, go to the “Views – add to category” section and add the ‘My Work’ set of views to the category. If you don’t add these views, migrated users will not be able to see any views when they navigate to the ‘My work’ page.

 

10)  Go to PWA->Server Settings->Operational policies->project workspace provisioning settings and choose ‘Automatically create a project workspace…” option. This is the more common option.  If you don’t want workspaces to be created automatically, you need not do this.

 

,
  • Tina
    16 Jun 2006 12:34 AM
    That's great!
  • Lidiane
    16 Jun 2006 1:12 AM
    I am glad you like it :)
  • David Lewis
    22 Jun 2006 12:20 AM
    I realize this is probably futile, but given all the attention over the years to whizzy new features, is there a chance of backfilling some bread and butter features that would make the basic project management processes oh so much easier?

    The prime exmaple in my book is tools to manage resource task sequences "by hand", including... (a) tagged links, so we can distinguish a link inserted to sequence/balance a resource from a logical dependency; (b) tools to quickly reassign tasks from one resource to another and (c) relink the task sequences easily, without having to manually rejigger the links.  

    Underlying all this is the -- very widespread -- observation that algorithmic resource levelling is...(how can I say this politely)... umm... useless (sorry), and the only way really to level is to manually sequence each resource's tasks.  

    There's much more along the same lines to deal with fractional assignments, multi-tasksing, coordinating tasks of different resoruces, etc etc, all in the same vein.  But what I've oulined above would be such a leap forward that I would fly to Redmond and hug the whole team!

    Sorry to hijack an irrelevant post for this rant, but after years of struggling with this stuff, I despair of ever being heard.  Aren't you gflad you have a blog? ;-)))

    Thanks for at least listening.

    David Lewis (djlewis at triadic dot com)
  • 22 Jun 2006 10:03 AM
    May I...ummm...disagree? Resource leveling is a great function in Microsoft Office Project if you have learnt how to use it. Better would be critical chain, of course, but I do not expect this seriously.

    Oliver
  • Igor Macori
    27 Jun 2006 9:43 AM
    Segnalo un bel post ricco di indicazioni e trucchetti per migrare il DB di Project Server da un ambiente...
  • Steffen
    29 Jun 2006 6:57 AM
    Do you work with SQL 200 or 2005? What ist the best way to migrate Project Server with SQL and 2007?

    I have a PS2003 on SQL and would like to migrate the database and the to the Beta2.

    thanks Steffen
  • Fraser Larcombe
    29 Jun 2006 9:12 PM
    I am actually having some problems installing the desktop version, it crashes at about 15% through the installation, does it every time, doesnt give me any idea of what has happened just says send info to MS, which I have done.

    Any ideas, anyone else had the same problem?

    Fraser
  • krishna
    10 Jul 2006 4:22 AM
    plz reply


    immedeatly
  • Lanka Van Dort - [email protected]
    26 Jul 2006 10:55 AM
    Accidentaly deleted some resources from the Global Database. How to recover the resources? Using MS Porject 2003 Enterprise version. Thanks!
  • Hrvoje
    8 Dec 2006 5:29 AM

    What about migration from Project Server 2007 Beta2 TR to RTM version ?

  • Rinat
    8 Jan 2007 2:07 AM

    What about migration of sharepoint workspaces?

  • Michael E
    9 Jan 2007 5:08 PM

    any suggestions on this failed upgrade?

    01/09/2007 15:51:41.414   Project Server 2003 version is 11,2,15,20030816

    01/09/2007 15:51:41.414   Time to execute CUpgrader::CheckP11Version(): 0 ms

    01/09/2007 15:51:41.414   preparing Query select WADMIN_DEFAULT_LANGUAGE from dbo.MSP_WEB_ADMIN

    01/09/2007 15:51:41.414   preparing Query select WADMIN_DEFAULT_LANGUAGE from MSP_WEB_ADMIN

    01/09/2007 15:51:41.424   preparing Query select isnull(is_member(?), 0)

    01/09/2007 15:51:41.424   preparing Query select isnull(is_member(?), 0)

    01/09/2007 15:51:41.424   preparing Query select isnull(is_member(?), 0)

    01/09/2007 15:51:41.434   preparing Query select isnull(is_member(?), 0)

    01/09/2007 15:51:41.564   preparing Query select VERS_VERSION from dbo.MSP_VERSIONS where VERS_DEFAULT = 1

    01/09/2007 15:51:41.574   preparing Query select UPG_PHASE_RUN_STATUS from dbo.MSP_P12UPGRADE_UPGRADE_RUN_PHASES where UPG_PHASE_UID=? AND UPG_PHASE_RUN_STATUS = ?

    01/09/2007 15:51:41.574   preparing Query exec dbo.MSP_P12UPG_INSERT_OR_UPDATE_RUN_PHASE_STATUS ?, ?, ?

    01/09/2007 15:51:41.594   preparing Query exec dbo.MSP_P12UPG_CreateAllViewsToProjectServer2003 ?, ?

    01/09/2007 15:51:41.604   Executing query failed with -1

    01/09/2007 15:51:41.604   Cmd failed retcode= -1

    01/09/2007 15:51:41.604   Err1 = 37000 Err2 = [Microsoft][ODBC SQL Server Driver][SQL Server]Could not find stored procedure 'dbo.MSP_P12UPG_CreateAllViewsToProjectServer2003'.

    01/09/2007 15:51:41.604   preparing Query exec dbo.MSP_P12UPG_INSERT_OR_UPDATE_RUN_PHASE_STATUS ?, ?, ?

    01/09/2007 15:51:41.614   PWA Migration: Setup Views to Project Server 2003 -- Failed.

    01/09/2007 15:51:41.614   Time to execute CUpgrader::UpgradePWASetupViews(): 40 ms

    01/09/2007 15:51:41.614   PWA Migration: Setup Views to Project Server 2003 -- Failed.

    01/09/2007 15:51:41.614   Updating run table

    01/09/2007 15:51:41.614   preparing Query update dbo.MSP_P12UPGRADE_UPGRADE_RUNS SET UPG_RUN_STATUS = ?, UPG_RUN_FINISH_DATE = GETDATE() where UPG_RUN_UID = ?

    01/09/2007 15:51:41.614   Executing Query update dbo.MSP_P12UPGRADE_UPGRADE_RUNS SET UPG_RUN_STATUS = ?, UPG_RUN_FINISH_DATE = GETDATE() where UPG_RUN_UID = ?

    01/09/2007 15:51:41.634   Migration finished with return code 80004005

    01/09/2007 15:51:41.634   Project migration failed.

  • Theron
    27 Sep 2007 10:50 PM

    Hi,

    Is there any procedure/steps when migrating from Project Server 2007 to Project Server 2007.

  • Anton Swanevelder
    27 Nov 2007 10:43 AM

    Thanks for this. It is a great help. Just a note for others: If your 2003 database is not yet upgraded to sp2a you can run the command line tool UPG10DB in the Utilities\Migration\Database folder on the Office Project Server 2007 installation media.

    http://technet2.microsoft.com/Office/en-us/library/f1606be4-f257-4469-a35a-d9189d542ce41033.mspx?mfr=true

  • Rully
    19 Mar 2008 5:57 AM

    I had problem how to migration Ms project 2007 from one database server to other database server.

    for the first installation, application, database reside on same machine server.

    how to migration database ms project to other server and aplication still in old server.

    thanks before

    Rully

Page 1 of 2 (30 items) 12