Schema Optimization to remove OOTB Pega DB objects
Below suggestions were made by the built-in Schema Optimization wizard, after the Pega application was successfully upgraded from 7.4 to 8.3.1 As these relate to the OOTB Schema objects created by Pega, can someone suggest if these objects can be safely removed without causing an issue?
---------------------------------------------------------
1. The columns listed below either have no corresponding properties defined or were exposed by one of the wizards like Property Optimization and not being used in Report Definitions. Please consider dropping these columns.
Below suggestions were made by the built-in Schema Optimization wizard, after the Pega application was successfully upgraded from 7.4 to 8.3.1 As these relate to the OOTB Schema objects created by Pega, can someone suggest if these objects can be safely removed without causing an issue?
---------------------------------------------------------
1. The columns listed below either have no corresponding properties defined or were exposed by one of the wizards like Property Optimization and not being used in Report Definitions. Please consider dropping these columns.
Table Columns
prpc_data.wm_logonroles specialroletype
prpc_data.wacdetails casestage
prpc_data.wacdetails createdatesortorder
prpc_data.wacdetails createdatetype
prpc_data.wacdetails isvalid
prpc_data.wacdetails lastrefreshedon
prpc_data.wacdetails ldesortorder
prpc_data.wacdetails numberwi
prpc_data.wacdetails pxindexcount
prpc_data.wacdetails pxindexpurpose
prpc_data.wacdetails pxinsindexedclass
prpc_data.wacdetails pxinsindexedkey
prpc_data.wacdetails tasktype
prpc_data.wacdetails taskurgencyfrom
prpc_data.wacdetails taskurgencyto
prpc_data.wacdetails wacname
prpc_data.wacdetails wacnotes
prpc_data.wacdetails workbaskettype
prpc_data.wacdetails yieldsortorder
prpc_data.wacdetails yieldtype
prpc_data.jiraint_pega_rule_event eventdetailpzinskey
prpc_data.edm_idx_role pxprivilegeclass
prpc_data.edm_idx_role pxprivilegename
prpc_data.edm_idx_role pyworkbasket
prpc_data.edm_idx_name pxprivilegeclass
prpc_data.edm_idx_name pxprivilegename
prpc_data.edm_idx_name pyaccessgroupadditional
prpc_data.cdcm_index_location pxprivilegeclass
prpc_data.cdcm_index_location pxprivilegename
prpc_data.cdcm_history_work pxlastsynctimestamp
2. It is possible that these tables were either created manually or the classes originally associated with these tables are not available. Removing these tables from the database will make the schema cleaner and contribute to better space utilization.
Table Instances
prpc_data.pr_data_dms_customer 0
prpc_data.pr_link_feature 290
prpc_data.pr_data_adm_toknmetadata 0
prpc_data.pr_file_upload_fallback 0
prpc_data.pr_data_dm_admmart_pred_fact 0
Pratik
Pegasystems Inc.
IN
Hello @pratik!
Please share the support case ID if you decide to create one.
Thanks,
Pallavi M | Moderator | Pega Collaboration Center
Cognizant
GB
Hello Pallavi,
The service request SR-90387 had to be withdrawn as GCS do not provide support for these queries.
Do you think GCS are able to provide some support now?
Pratik Agarwal
Pegasystems Inc.
IN
Hello,
I do not think things have changed now.
However, I am hopeful you will get some helpful answers here.
Regards,
Pallavi M | Moderator | Pega Collaboration Center
Pegasystems Inc.
IN
Hi,
By looking at the table name mentioned in Q1, it seems they don't belong to pega platform, have you also upgraded any pega framework/strategic applications along with framework(the tables could be part of some pega framework), so in that case you may decide based on what suits your application,however there is no harm leaving them as it is.
The tables mentioned in Q2 are OOTB tables,for example pr_link_feature tables is part of ootb rules schema mapped to Link-Feature class, so i would like to know, does your application have single schema or split schema.
You might have got this list from Optimize Schema landing page, if not you can please check the same for more details.
Regards,
Mritunjay Kumar
Cognizant
GB
Hi @kumam7 Your assumptions are correct.
These recommendations are from Optimize Schema landing page.
Q1 can be ignored as these are custom db objects.
Q2 objects still need to be confirmed before dropping.
The application is on a split schema architecture with separated Rules and Data.
Please advise.
Pratik Agarwal