Posted: 12 Jan 2016 14:03 EST Last activity: 17 Jan 2016 2:00 EST
Some Tables from OOTB Pega 7 are missing primary keys on them
There are some tables in pega 7 ( we are using Pega717/718) which do not have Primary keys defined on them. For example pr_sys_updatescache and pr_index_Info. In some of our client places when trying to upgrade to Pega7 or creating new Pega7 environment the Client Database teams are rejecting creation of such tables with out primary keys. GCS recommended us to post this question here. I am looking for details/info around why these tables deliberately left without a primary key by pega , and are there any plans for pega to add keys to these tables in future. If client insists on standards can we go ahead an create a new column and make it primary key. What are Pega's thoughts around this.
Both tables exist before Pega 7. pr_sys_updatescache is an internal table used for sync up rules updates cross multi-nodes. There is no need of primary key. pr_index_info is used for previous release in AES. It is already gone. There is no plan to add primary key for updatescache table.