Note: The scripts described in this procedure are on the P6 Professional physical media or download.
To upgrade your database:
- Log in to Microsoft SQL Server Management Studio as the sa user.
- Go to \database\scripts\common and run the ss_disable_triggers.sql script.
- Go to \database\scripts\upgrade\PPM_<release_level> and run one of the following scripts:
SSPPM_p70sp1.sql, if upgrading from P6 Professional 7.0 and 7.0 Service Pack 1
SSPPM_p70sp3.sql, if upgrading from P6 Professional 7.0 Service Pack 3
SSPPM_p70sp5.sql, if upgrading from P6 Professional 7.0 Service Pack 5
SSPPM_p81.sql, if upgrading from P6 Professional 8.1
SSPPM_p81sp1.sql, if upgrading from P6 Professional 8.1 Patch Set 1
SSPPM_p82.sql, if upgrading from P6 Professional 8.2
SSPPM_p82sp1.sql, if upgrading from P6 Professional 8.2 Patch Set 1
SSPPM_p82sp3.sql, if upgrading from P6 Professional 8.2 Patch Set 3
SSPPM_p83.sql, if upgrading from P6 Professional 8.3
SSPPM_p83sp2.sql, if upgrading from P6 Professional 8.3 Patch Set 2
SSPPM_p83sp3.sql, if upgrading from P6 Professional 8.3 Patch Set 3
SSPPM_p84.sql, if upgrading from P6 Professional 8.4
SSPPM_p841.sql, if upgrading from P6 Professional 8.4 Patch Set 1
SSPPM_p843.sql, if upgrading from P6 Professional 8.4 Patch Set 3
SSPPM_P151.sql, if upgrading from P6 Professional 15 R1
SSPPM_P152.sql, if upgrading from P6 Professional 15 R2
SSPPM_P161.sql, if upgrading from P6 Professional 16 R1
SSPPM_P162.sql, if upgrading from P6 Professional 16 R2
- 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.
- Go to \database\scripts\common and run the ss_post_upgrade.sql script.
- Go to \database\scripts\source\PPM_<release_level> and run the ssppm_grants.sql script.
Note: If you changed the default user names, you must update the privuser and pubuser names in this script with your custom user names.
- Go to \database\scripts\source\PPM_<release_level> and run the ssppm_synonyms.sql script.
Caution: The ssppm_synonyms.sql script contains a table called PUBUSER. Do not replace it if you have to change the pubuser user name.
Note: If you changed the default user names, you must update the privuser and pubuser names in this script with your custom user names.
- Go to \database\scripts\source\PPM_<release_level> and run the ssppm_src.plb script.
Notes:
- If you changed the default privuser name, you must update the ssppm_src.plb script with your custom privuser name.
- Do not use special characters in the database name, privileged user, or public user name, for example: { } [ ] : ; < > , . ? ! @ # $ % ^ & * ( ) - _ | / \ ~ `
- Go to \database\scripts\source\PPM_<release_level> and run the ssppm_init_bgjobs.sql script.
- Go to \database\scripts\install\PPM_<release_level> and run the ssppm_database_version.sql script.
- Go to \database\scripts\install\PPM_<release_level> and run the ssppm_querylib.sql script.
- Go to \database and run databaselogins.bat (on Windows) or databaselogins.sh (on Unix) to upgrade the encryption of privilege user passwords. See Private Database Credentials for P6 Professional for more information.