Close popover
Rob Jago (Rob_Jago)
Senior Consultant
Rob_Jago Member since 2015 41 posts
Posted: July 28, 2016
Last activity: August 1, 2016

Migration of History tables for Work items and data items. How to address if they were initially missed? which ones should be [now] migrated without impacting performance/functionality?


using Pega 7.1.8, we have performed a few migrations to a test environment.  Via some performance/optimization testing we discovered that we had mistakenly not migrated any Work item History table definitions.  (one item that led us down this path was that optimized fields in DEV did not result in the appropriate column add SQL statements being generated when migrating to a different environment)   When performing the packaging wizard, it was observed that a LOT of History items were identified to be migrated.   The concern is that some previous coding mistakes has resulted in this list being large.  We would like to minimally add only the necessary history tables and thus minimize the potential impact on functionality/perfomance in the test environment.  (And then migrate the data from pr_history into the new history tables as appropriate)   What is the normal best practice?   And given that, how should we proceed in fixing this.? 

***Updated by moderator:Marissa. Removed user added Ask the Expert and #helpme tags. Apologies for confusion, shouldn't have been an end-user option***

Data Integration
Moderation Team has archived post,
Close popover This thread is closed to future replies. Content and links will no longer be updated. If you have the same/similar Question, please write a new Question.