Upgrading the P6 EPPM Microsoft SQL Server Database

To upgrade the P6 EPPM Microsoft SQL Server Database:

  1. If you haven't done so, download the Primavera P6 Enterprise Project Portfolio Management R<release_level> for <platform> folder and extract the contents.
  2. Go to the location of the extracted contents and locate the P6_R<release_level>\p6suite\database folder.

    Notes:

    • Make a backup copy of any files you will modify before you edit them.
    • You need to run all the scripts included in this section against PMDB to upgrade.
  3. Open Microsoft SQL Server Management Studio and log in as the SA user.
  4. Go to \scripts\install\PM_<release_level> and run the sspm_create_plus_users.sql script.

    Notes:

    • Running the sspm_create_plus_users.sql script creates the following user name: PxRptUser. If you have created another user name and wish to use that when running P6 EPPM database scripts, make sure to replace the PxRptUser name with your custom user name in all applicable scripts before running them.
    • Do not use special characters in the database name, privileged user, public user, or PX reporting user name, for example: { } [ ] : ; < > , . ? ! @ # $ % ^ & * ( ) - _ | / \ ~ `
  5. Go to scripts\common and run the ss_disable_triggers.sql script.
  6. Go to \scripts\upgrade\PM_<release_level> on your local drive. Run one of the following scripts that is closest to the version of P6 EPPM that you are trying to upgrade:
    • SSPM_p70sp1.sql, if upgrading from P6 version 7.0, 7.0 service pack 1, or 7.0 service pack 2
    • SSPM_p70sp3.sql, if upgrading from P6 version 7.0 service pack 3
    • SSPM_p70sp5.sql, if upgrading from P6 version 7.0 service pack 5
    • SSPM_p80.sql, if upgrading from P6 version 8.0
    • SSPM_p81.sql, if upgrading from P6 version 8.1
    • SSPM_p81sp3.sql, if upgrading from P6 version 8.1 service pack 3
    • SSPM_p82.sql, if upgrading from P6 version 8.2
    • SSPM_p82sp1.sql, if upgrading from P6 version 8.2 service pack 1
    • SSPM_p82sp2.sql, if upgrading from P6 version 8.2 service pack 2
    • SSPM_p82sp2f10.sql, if upgrading from P6 version 8.2 service pack 2 Hotfix 10
    • SSPM_p83.sql, if upgrading from P6 version 8.3
    • SSPM_p832.sql, if upgrading from P6 version 8.3 service pack 2
    • SSPM_p833.sql, if upgrading from P6 version 8.3 service pack 3
    • SSPM_p834.sql, if upgrading from P6 version 8.3 service pack 4
    • SSPM_p835.sql, if upgrading from P6 versions 8.3 service pack 5
    • SSPM_P84.sql, if upgrading from P6 version 8.4
    • SSPM_p841.sql, if upgrading from P6 versions 8.4 patch set 1
    • SSPM_p843.sql, if upgrading from P6 versions 8.4 patch set 3
    • SSPM_P151.sql, if upgrading from P6 version 15.1
    • SSPM_P152.sql, if upgrading from P6 version 15 R2
    • SSPM_P161.sql, if upgrading from P6 version 16 R1
    • SSPM_P162.sql, if upgrading from P6 version 16 R2
  7. If you are using version 7.0 or later, skip to the next step.

    If you are using version 6.21 or earlier, go to \scripts\common and run the ss_update_usereng.sql script to grant all users with P6 Professional module access rights to the Projects section in P6.

    Note: Prior to P6 version 7.0, users with Project Management module access also had rights to the Projects section in P6 Web Access. For security reasons, beginning with P6 version 7.0, P6 Professional module access only grants rights to log into the P6 Professional module.

  8. Go to \scripts\common and run the ss_post_upgrade script.
  9. Go to \scripts\upgrade\PM_<release_level> and run the sspm_grants.sql script.

    Note: If you changed the default user names, you must update the privuser, pubuser, and PxRptUser names in this script with your custom user names.

  10. Go to \scripts\upgrade\PM_<release_level> and run the sspm_synonyms.sql script.

    Caution: The sspm_synonyms.sql script contains a table called PUBUSER, do not replace it if you have changed the pubuser user name.

    Note: If you changed the default user names, you must update the privuser, pubuser, and PxRptUser names in this script with your custom user names.

  11. Go to \scripts\source\PM_<release_level> and run the sspm_src.plb script.

    Notes:

    • If you changed the default privuser name, you must update the sspm_src.plb script with your custom privuser name.
    • Do not use special characters in the database name, privileged user, public user, or PX reporting user name, for example: { } [ ] : ; < > , . ? ! @ # $ % ^ & * ( ) - _ | / \ ~ `
  12. Go to \scripts\install\PM_<release_level> and run the sspm_database_version.sql and sspm_querylib.sql scripts.
  13. Go to \scripts\common and run the ss_enable_constraints_triggers.sql script.
  14. Go to \scripts\install\PM_<release_level> and run the sspm_init_bgjobs.sql script.
  15. Run the databaselogins.bat (on Windows) or databaselogins.sh (on Unix) to upgrade the encryption of privilege user passwords.
  16. Log into the P6 EPPM database as PxRptUser or use your custom PX reporting user name if you created one.
  17. Go to scripts\source\PM_<release_level> and run the sspm_px_rpt_src.sql script.

Last Published Friday, August 8, 2025