Question

1
Replies
1471
Views
 Debashish Majumdar (KnowHowPRPC)
TCS

TCS
IN
KnowHowPRPC Member since 2011 16 posts
TCS
Posted: March 19, 2019
Last activity: April 25, 2019
Posted: 19 Mar 2019 17:02 EDT
Last activity: 25 Apr 2019 8:36 EDT
Closed
Solved

Split Schema in Pega 7

What is the advantage of split schema in Pega 7 from developer or performance aspects?How the two schemas PegaRules(for Rule instances) and PegaData (for Work and Data instances) is an advantage over single schema in Pega 6?

***Edited by Moderator Marissa to update platform capability tags****

Pega Platform System Administration
Moderation Team has archived post, This thread is closed to future replies. Content and links will no longer be updated. If you have the same/similar Question, please write a new Question.

Accepted Solution

Posted: 2 years ago
Posted: 19 Mar 2019 19:05 EDT
Susan Liu (SusanLiu_GCS)
PEGA
Principal Software Solutions Engineer
Pegasystems Inc.
US

Please check below link


https://community.pega.com/knowledgebase/articles/high-availability-whats-new-pega-7


in the section Upgrade production PRPC.


“Split schema” refers to the idea of classifying the database tables used by PegaRULES into two categories : Rules tables and Data tables.



The primary goal for this is to decrease the amount of time a system must be unavailable during an upgrade. As such, this epic is a key part of the “high availability” goal.



The principle behind this idea is that rules change significantly from one release to the next, whereas data and work transcend releases. During an upgrade, one would install a completely new set of rules tables, while keeping the data tables (essentially) untouched.