Skip to main content

Table of Contents

Configuring a split database architecture


Only available versions of this content are shown in the dropdown

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.

Did you find this content helpful?

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 Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us