+5Add option in Storage management task to clean the ‘_PK’ tables in the ODX database. I've created a topic a while ago about the ‘_PK’ tables are growing rapidly in terms of disk space. To avoid having bigger ‘_PK’ tables then ‘DATA’ tables in the ODX, it would be great this table can be cleaned. I think the storage management task would be the place to do it. You should be able to set the maximum number of batches that need to be saved in the ‘_PK’ tables.
As a reference:
+8As an addition I would like an option to prevent older states being kept in the first place. There should only be a ‘last’ set in the _PK table which can be compared against the ‘new’ state in tempdb and swapped out.
+5Hey
Functionality soon to also be added to SaaS as well.
+5
I'm using a SQL DB as ODX storage.
Could you elaborate on how to find/use this new feature?
+5Hi
We also have an issue with the PK tables growing exponentially in size.
+5
Hi
I have received a notification in my email about an update in January/February '26. Is this still on the roadmap?
Thanks!
Kind Regards,
Tom Maarsen
+5Hi
This has been released now in 7257.1. Please see release notes for reference:
To reduce the size of the PK tables, please upgrade to this version and run the incremental load task to reduce the size of existing PK tables
FYI
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
