Difference in CustomerData and PegaData for Pega database table
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?
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?
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!