Hi Lars,
Sorry about the alignment. The no_merge_results.csv should have the data aligned better.
I did check the m_merge_delta_statistics view and can see 12 errors for "column store error:[2482] table optimization was not indicated".
In the Hana troubleshooting and performance analysis guide it says if this error occurs frequently review the smart merge cost function with SAP experts. We currently have the default setting for the smart merge formula.
One thing to note is we see this error on the first iteration where we saw the $delta$ container space released.
I also tried merge delta of <table> with parameters ('FORCED_MERGE' = 'ON') and saw the 2482 error.
When looking at the total memory used for the PRICAT_K008C table it is only using 12.6GB of space. The $delta$ container is using 74.6GB of persistence space.
I also tested loading the table into memory and see that the larger $delta$ space slows down the load time even though it appears to be empty.
I appreciate your time for this discussion.
Thanks,
Troy