Posted: 19 Jun 2018 7:27 EDT Last activity: 29 Jun 2018 9:41 EDT
Segregate table generated by Pega Marketing
When we are running campaign, it will generate internal table like pr_xx in our databases. These
tables are getting out of hand when we have more campaigns. I have my customer database withthin the same schema. I want to bring out my customer database into another DB leaving pega marketing to write out in the existence db schma. Is this feasible. Tried, but the internal table wrote to the same schmea where I stored the customer data
the PRxxx tables generated during campaign run and Customer data needs to be in the same schema, i think it is by design.
the PRxxx table is needed for other PM functionality which runs post Campaign runs for ex, Wait functionality on offer flows run by processofferwaitflow agent, and needs to make a join with Customer table.
are you observing that older PRxxx are not getting deleted? The batch classes and tables generated during campaign runs are cleared by ProcessPurging agent. Please check if this agent is running. It runs daily and and should be configured to run only on one node.