Need Approach/steps to split existing PEGA schema to PegaRules and PegaData

Planning to implement split schema during our app upgrade from Pega 8.8.2 to 24.1, Need direction/steps from Pega support

@KrishnaKG

Pega Platform supports a split schema database architecture, which separates rules and data into separate schemas. This is essential for enabling minimal to zero downtime during Pega Platform application and strategic application upgrades or patch installation.

During the upgrade, you can migrate the upgraded rules schema to the higher environment and do the data schema only upgrade. However, you will need to go through the same steps for upgrading the strategic apps as you did in the lower environment.

Please note that you cannot run two versions of Pega Platform against the same PegaDATA schema at the same time. The newer version of Pega Platform might make changes to cases and data that are not forward compatible, resulting in the older Pega Platform version unable to process the updated cases and data.

:warning: This is a GenAI-powered tool. All generated answers require validation against the provided references.

Data Schema Upgrade for Higher Environments

Understanding a split database architecture > Split schema database architectu

Planning a Pega Platform installation > Understanding Pega Platform split-schema architecture

Performing your update

Patching systems without downtime (for Pega Platform version 8.4 and later)