Discussion

7
Replies
311
Views
 Fran Collins (COLLF-1)
PEGA
Director, Consulting
Pegasystems Inc.
JP
COLLF-1 Member since 2012 21 posts
PEGA
Posted: March 17, 2016
Last activity: April 6, 2018
Posted: 17 Mar 2016 4:55 EDT
Last activity: 6 Apr 2018 19:26 EDT
Closed

Pega 7.1.6 to Pega 7.1.8 - Data Schema Changes

Hello,

On Page 34 of the Update Deployment Guide, Step #4, there are instructions on how to execute the Data Schema update to Pega 7.1.8. We will be making this update from Pega 7.1.6.

Before we manipulate the schema containing the client's data, we need to assure them that the changes to the Data Schema will not impact their data. In order to reassure them, they are asking for a high-level list of the changes to be made to the Data Schema.

Can someone please provide that information? We need it to begin our update.

Thank you!

- Fran

**Moderation Team has archived post**

This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.

System Administration Upgrades
Moderation Team has archived post, This thread is closed to future replies. Content and links will no longer be updated. If you have the same/similar Discussion, please write a new Discussion.
Posted: 5 years ago
Posted: 17 Mar 2016 5:20 EDT
Dhevendra Earva (earvd)
PEGA
Senior Manager, Cloud Engineering
Pegasystems Inc.
IN

You can run the generateDDL utility with UpgradeDataOnly true option in Pega 7.1.8 distribution image that will give you all the alter statements which is required from Pega 7.1.6 to Pega 7.1.8 update. Running this statement will not impact on your current 7.1.6 system as its generates only DDL delta changes between7.1.6 to 7.1.8.


 
Posted: 5 years ago
Posted: 17 Mar 2016 20:37 EDT
Fran Collins (COLLF-1)
PEGA
Director, Consulting
Pegasystems Inc.
JP

Hi Dhevendra,


Thank you for this information. We will make sure to do this, if we must. However, there is no high-level explanation or documentation which can be provided? We have to analyze the DDL generated by the utility? I ask because our time is at a premium, so if there is any existing reference material, that would same us having to review and understand what could be potentially ambiguous DDL statements, which is potentially time-consuming.


Let me know.


Thank you!


Fran
Posted: 5 years ago
Posted: 18 Mar 2016 1:07 EDT
Dhevendra Earva (earvd)
PEGA
Senior Manager, Cloud Engineering
Pegasystems Inc.
IN

Hi Fran,


The generated DDL contains only delta changes between Pega 71.6 to Pega 7.1.8. This utility will compare your current schema (Pega 7.1.6) with OOTB Pega 71.8 schema then generates the delta DDL. Once you generate the DDL you should be able to find all the schema changes. This utility may take 5-10 minutes to execute.


As per I know there are two columns (pxCommitDateTime and pxSaveDateTime) are added for  all the tables in data schema.


Thanks,


Dhev
Posted: 5 years ago
Posted: 22 Mar 2016 4:42 EDT
Fran Collins (COLLF-1)
PEGA
Director, Consulting
Pegasystems Inc.
JP

Hi Dhevendra,


So there is no other source of information for determining the data schema changes between Pega 7.1.6 and Pega 7.1.8, other than to generate the DDL? There is no documentation that details the data schema deltas per release?


Please let me know your response. I do not want to have to generate and then interpret a DDL if I do not have to.


Thank you!


Fran
Posted: 5 years ago
Posted: 17 Mar 2016 10:05 EDT
Sudharsan Raman (sudharsan)
PEGA
Principal Software Engineer - Customer Success
Pegasystems Inc.
IN

Hi,


The following are the list of high level steps followed in the ML update process for PRPC 7.1.8,


  1.             Initialization,

  2.             Configuration,

  3.             Verify ML Readiness,

  4.             Cleanup RuleSets,

  5.             Generate Upgrade DDL,

  6.             Schema Upgrade,

  7.             Apply UDFs,

  8.             Engine Load,

  9.             Reorganize Database Indexes Preupgrade,

  10.             Remove Invalid Settings,

  11.             Rules Upgrade,

  12.             Reorganize Database Indexes,

  13.             Calculate Table Stats,

  14.             Upgrade Rule Messages,

  15.             Generate Declarative Indexes,

  16.             Import Assembled Classes,

  17.             Log Schema Meta Data,

  18.             Import Updates,

  19.             Update Existing Applications,

  20.             Run Assembler,

  21.             Prebuild Conclusions,

  22.             Truncate Updates Cache,

  23.             Cleanup

AFAIK, there are no steps which manipulate the existing work object data during ml update. Is this information sufficient ?


Thank you

Sudharsan
Posted: 5 years ago
Posted: 17 Mar 2016 20:40 EDT
Fran Collins (COLLF-1)
PEGA
Director, Consulting
Pegasystems Inc.
JP

Hi Sudharsan,


Thank you for the information. Unfortunately, I am looking for an explanation or documentation regarding the changes made in the Data Schema for an update from Pega 7.1.6 to Pega 7.1.8. The explanation you provided is quite helpful for an overview of the entire update process, but I am looking for actual changes versus process.


If you can let me know the high-level changes made to the Data Schema between Pega 7.1.6 and Pega 7.1.8, that would be very helpful.


Thank you!


Fran
Posted: 5 years ago
Posted: 11 Apr 2016 14:42 EDT
Bill Rathert (rathw)
PEGA
Global Tech Enablement, Principal Instructor
Pegasystems Inc.
US

Majority of the data schema changes in Pega 7.1.8 are the addition of the pxSaveDateTime (when a save request is issued by the PRPC Rule space) and the pxCommitDateTime (when the INSERT/UPDATE is executed). 
 
You can view the scripts for database changes between Pega 7.1.7 and Pega 7.1.8 that are created in the directory 'scripts'. 


Differences between 7.1.7 and 7.1.6:


https://pdn.pega.com/sites/pdn.pega.com/files/help_v72/procomhelpmain.htm#database/database2/databasetablesdata.htm


Thanks,


Bill