Question

6
Replies
72
Views
Pratik A (pratik)
Cognizant Technology Solutions
Strategic Solution Architect
Cognizant Technology Solutions
GB
pratik Member since 2013 13 posts
Cognizant Technology Solutions
Posted: September 14, 2020
Last activity: 5 days 21 hours ago
Posted: 14 Sep 2020 11:01 EDT
Last activity: 10 Sep 2021 15:43 EDT

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

***Edited by Moderator Marissa to update Platform Capability tags; update Support Case details****
Pega Platform 8.3.1 Data Integration Support Case Created Upgrade