Skip to main content


         This documentation site is for previous versions. Visit our new documentation site for current releases.      
 

Split schema database architecture

Updated on May 11, 2022

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.

Have a question? Get answers now.

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

Did you find this content helpful?

Want to help us improve this content?

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