Hi!
I have created a post recently where we are discussing the clean-up of old version modules using DBCleanerOnSteroids and the High Records on Module_PublicElement Database Entity from Service Center (OSSYS_MODULE_PUBLICELEMENT) Module_PublicElement Increasing Database (OSSYS_MODULE_PUBLICELEMENT)
As part of a further investigation and my last comments there, it is related to this Forge Asset
And as stated on my last Comment or I'm missing any step on using DBCleanerOnSteroids or DBCleanerOnSteroids doesn't take this Database Entity in consideration
Too even more details this is what contains the Database Entity in question, where I believe that "Producer_SS_KEY" Entity Attribute is the Foreign Key to the Espace Module Version Database Entity
Greetings,Pedro Vieira
As part of the platform server release notes I discovered that this table is also clean-up by Service Center it self
The Timer UnusedElements_Cleanup should clean up the records from the OSSYS_MODULE_PUBLICELEMENT table, but it was failing with a timeout. This could impact publishing from Service Studio. (RPM-2241)
This timer is executed automatically at day 1 of each Month
Our database shines now!
Thanks for the amazing component!Greetings,Pedro Vieira
Hi, With a bit more investigation using SQL Sandbox:Before Deleting the Module and his Versions:
After Deleting the Module and his Versions:
Hey Pedro!
Nice finding! We're using the internal DBCleaner_API, probably there's the bug. But I'll take a look into your findings and see what can be done in the component. Thanks for all this info!