Skip to main content

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

Configuring a split database architecture

Updated on August 25, 2021

Pega Platform high availability is database-agnostic. The recommended database features are:

  • Highly available clustered databases or third party or database vendor software that supports this feature
  • Database fault tolerance that meets production service level agreement requirements — for example, some databases have add-on products to handle failover of hardware or software sub-systems, enabling another piece to take over

For supported database platform versions, see the Platform Support Guide on Pega Community.

  • Split schema database architecture

    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.

  • Replicated and split databases

    In general, the Pega Platform data can be replicated or split to support high-volume production requirements, reporting, or other needs.

  • Previous topic Understanding the unique features of the Pega Platform database
  • Next topic Split schema database architecture

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. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us