Configuring Data Retention and Data Purge Policies
J
Joseph. g. patton
started a topic
7 days ago
Hello All,
I have a quick question regarding data retention policies and purge jobs for Semarchy xDM data hubs. Master History(MH_) and Golden History(GH_) tables make up most of the top 20 objects in our Semarchy database environments. Our data models currently have no data retention policies. We have also grown the number of our Semarchy xDM non-prod environments in recent months. I'm just looking for ideas on how to trim the storage footprint of our non-prod environments after running a refresh from the production environment. I would probably leave our QA environment alone, but I'm thinking about setting a minimal data retention policy in our other non-production environments and scheduling purges to reduce the size of the data hub history tables. I would be interested in hearing about any other ways to slim down our lower Semarchy xDM environments after refreshing from the production environment.
Joseph. g. patton
Hello All,
I have a quick question regarding data retention policies and purge jobs for Semarchy xDM data hubs. Master History(MH_) and Golden History(GH_) tables make up most of the top 20 objects in our Semarchy database environments. Our data models currently have no data retention policies. We have also grown the number of our Semarchy xDM non-prod environments in recent months. I'm just looking for ideas on how to trim the storage footprint of our non-prod environments after running a refresh from the production environment. I would probably leave our QA environment alone, but I'm thinking about setting a minimal data retention policy in our other non-production environments and scheduling purges to reduce the size of the data hub history tables. I would be interested in hearing about any other ways to slim down our lower Semarchy xDM environments after refreshing from the production environment.
Regards,
Joe Patton