Pega 7 supports split schema database architecture which is useful to perform PRPC upgrades that minimally impact the user experience. The split schema separates rules and data by saving them into separate schemas. Splitting schemas enables minimal to zero down time during PRPC, application, and framework upgrades or patch installation. PRPC System Administrators can install and upgrade a new rules schema in the production database while the old schema is still in use. Pega 7 high availability features can then be used to move users from the old rule schema to the new schema on the production system to complete the upgrade.

The steps to do this upgrade are:

3. Freeze rule development in the existing system

4. Create a new schema

5. Migrate rules from the old schema to the new schema

6. Upgrade the new schema to a new PRPC release

7. Update the data instances in the existing data schema

8. Modify the DB connections to point to the new schema

9. Quiesce one server after another to perform a rolling start