Skip to main content

 –

Split schema database architecture

Suggest edit Updated on November 30, 2021

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

The use of split schema architecture enables Pega Platform System Administrators to install and upgrade a new rules schema in the production database while the old schema is still in use. Pega Platform high availability features can then be used to migrate users from the old rule schema to the new schema on the production system to complete the upgrade.

Did you find this content helpful? YesNo

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Ready to crush complexity?

Experience the benefits of Pega Community when you log in.

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us