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****
“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.