Posted: 26 Feb 2019 8:36 EST Last activity: 28 Feb 2019 9:21 EST
Removing unused tables from rules and data schema post upgrade 6.4 to 7.2.2
During upgrade pegarules was copied to pegadata, but still we can find tables which is mapped to pegadata and pegarules as well. So we need to remove redundant tables. Is it fine to have tables which is present in both the schemas even though it is not mapped to application?
Even though some do not have content in one scheme but in the other, it seems that the definition of the tables must be present in both schemes. If we try to remove them then it gives errors in pega. For example, you would expect the PR4 tables only in pegarules. But there is a routine which is looking for in pegadata.
PC_INDEX_ACCEL no data most recent DDL in dev PEGARULES
PC_INDEX_FLOWREF no data most recent DDL in dev PEGARULES
PC_INDEX_LOCATION no data most recent DDL in dev PEGARULES
PC_INDEX_WORKPARTY only data in PEGADATA
PR_INDEX_ACCESSGROUPROLES most recent data PEGADATA
PR_INDEX_ACCESSGROUPWKPOOLS most recent data PEGADATA
PR_INDEX_PRIVILEGE different table structure (Last DDL most recent PEGADATA )
PR_LICENSE_PARAMETERS most recent DDL in dev PEGADATA ( in Prod equal )
PR_SYS_STATUSNODES most recent data PEGADATA
PR_SYS_WORKINDEXER_QUEUE mixt image old data in both no data in prod PEGADATA but oldest DDL PEGARULES dev
PR4_HISTORY_RULE only data in PEGADATA
PR4_LOG_RULE_USAGE mixt image recents data in PEGADATA , but most recent DDL Pegarules
PR4_LOG_RULE_USAGE_DETAILS only data in PEGADATA Prod
PR4_RULE most recent data in PEGARULES
PR4_RULE_AUTOTEST old data most recent DDL in dev Pegadata
PR4_RULE_FILE most recent data PEGARULES
PR4_RULE_FLOW most recent data PEGARULES
PR4_RULE_PROPERTY most recent data PEGARULES
PR4_RULE_SHORTCUT most recent data PROD PEGARULES
So the question is how to remove unused tables ? So that we can improve our performance.
***Edited by Moderator Marissa to update platform capability tags****
There should only be one mapping between each class and table, so this should go to one of the two schema. If you're finding there are dependencies on having the table in both, this may need to be examined further.
For the duplicate table clean-up you should be able to do this in the "Cleaning up unused tables" section of the upgrade guide
Thanks Laurence for your insights. But the thing is as we upgraded from Pega 6 to Pega 7.2.2 we went for split schema. In Pega 6 it was single schema.
In 7.2.2 Pegarules and Pegadata both are having redundant tables.The tables which must be present in Pegarules is also present in Pegadata and vice-versa? Now we want to remove the redundant tables from both the schemas.