Skip to main content

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

This content has been archived and is no longer being updated.

Links may not function; however, this content may be relevant to outdated versions of the product.

Replicated and split databases

Updated on April 5, 2022

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

Database vendor facilities that implement replication do not affect the Pega Platform operation. Separate server nodes can access tables in separate, but synchronized, database instances.

Caution: Never replicate the pr_sys_updatescache or pr_sys_locks tables. All nodes in a multinode Pega Platform system must access a single copy of these two tables.

In addition, in a production system the rules change slowly and frequently used rules are cached. Work items, work item history, and work item attachments can grow to require more space than rules.

  • Previous topic Split schema database architecture
  • Next topic Viewing database tables and Pega Platform metadata by using the Clipboard tool

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