Batchout Table and Batchout Table_VC
Hi,
We are running a campaign and pega creates 2 tables.
One with all the Strategy result properties as columns -> BatchoutXXX. And a similar table with VC appended.
My question is : What is the internal mechanism; what kind of query does pega do to the tables to apply the volume constraint on the campaign results? Does it create another temporary table?
I am curious about the query and the boundaries it gives us.
Kind regards,
Joost Spekschoor
Thnx for your answer. We will look into the proposed hotfix.
The problem we faced with the merge statement caused errors in the database, length of properties X amount of columns > 32k..
Our workaround was to identify properties as transient and to shorten the length of properties. Giving no lenght gives them default 32 length.
The queries are pretty simple read from 1 table (select *) and write to the next table (insert *). All of the constraint logic is done internally in proprietary code between these two steps to do the volume constraint and optimization.
Please note that the insert statement in some versions of Pega Marketing was a merge statement due to a bug in the database layer. There is a hotfix that has been supplied to your account for this specific issue, which caused some paging issues in DB2.