Difference in CustomerData and PegaData for Pega database table
Hi All,
Can advise what is the different in the CustomerData and PegaData in the database table? When I create a custom table for a new class, is it advisable to save it under Customer Data instead of PegaData? Will there be any difference on migrating those tables when we upgrade Pega version?
Thank you!
Pegasystems Inc.
GB
Hi,
Pega data can be migrated automatically in normal way according to upgrade guide. Regarding Custom tables you can refer below link :
https://collaborate.pega.com/question/pega-upgrade-migrating-custom-tables
Updated: 13 Apr 2020 9:29 EDT
Pegasystems Inc.
IN
Hi,
CustomerData:
The Database schema in which all the table created will not have any pega default columns like pxcreatedatime, pxupdatedatetime etc... and no blob in it.
PegaData:
The Database schema in which all the table created will have few pega default columns like pxcreatedatime, pxupdatedatetime etc... and blob in it.
Other than these there is no major difference. based on the business need, choose the proper one.
Regards,
Mohan
Accenture
SG
Thanks both for answering my question.
To be more specific, the CustomerData schema we used still creates Pega related tables under pegaDATA, and there are some OOTB columns generated for this table as well. Trying to understand, if we are creating a Data Type for maintainable data pages for user to key in some configurable values, the records still store in Pega DB but when setting the data class to db table mapping, is it advisable to use CustomerData or PegaData schema?
Thank you.
Pegasystems Inc.
IN
as of today CustomerData and pegaDATA both are pointing to same DB, but in future CustomerData schema might not point to same DB. So it is advised to use CustomerData for all user created datatypes <---> Table mapping.
You won't face any issues in future upgrades, if you follow this!