Outstanding Contributor.
Outstanding Contributor.

[Webinar] OO Database purging recording available

Hi guys,

March 17 webinar is already available in the webinar playlist or directly here.

The unanswered questions from the webinar will be handled in this topic later (hopefully this week) by OO RnD.

Thank you all. See you next month.

Best regards,

Andrei Vasile Truta

Andrei Vasile Truta
1 Reply
Micro Focus Expert
Micro Focus Expert

Hi everyone,

I will post below the final questions from the webinar together with their answer:


Q: How about OO installer creates vendor specific purge procedures in the DB? Then the flows /API could call those procedures to take advantage of native performance gains
A: We are looking into both possibilities of improving the APIs related to purging as well as the overall experience, however this particular option at this time is not implemented due to in part the limited availability of scripts, scenarios where database access from OO is severely limited (no DDL scenarios) and concerns regarding safeguards which we may or may not be able to implement (to name a few). The installer needs to work under a “one size fits all” mode and as such before we add any new option to the installer we first need to ensure that the new option will respect this principle.

Q: It would be nice if the flows could report the total rows deleted in the DB in addition to the records “Removed xxx records using yyy rows”
A: We have an enhancement request to improve the data reporting of the flows in the system and we will look at both flow and api capabilities to improve this when the enhancement request will be handled.

Q: Is there any issue with simply scheduling the desired purge flows at the desired retention to run daily? The db size should never get out of hand..
A: There is no issue with this whatsoever, in fact on certain internal environments we actually schedule the purge execution summary to run several times per day with the given retention period and as such we keep the data that needs to be deleted on every purge execution to a minimal. If you plan to do this just make sure to schedule the flow in accordance to the retention period type you want (as described in the webinar) and according to the activity of the central in order to schedule the flow at a relative low activity period.


Thank you for attending,

Vlad Moldovan

The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.