David Foard · Mar 29, 2021

Purge strategy for parent-child persistent objects

We are seeing performance issues in purging objects/tables that have parent-child relationships defined. Due to the number of child objects we're seeing very long duration to purge a single parent and all child tables. Is there a better way to do this and get a more performant purge task? I was thinking to purge the child tables individually first and then delete the parent is one way. Is there any other approach?



Product version:
IRIS 2020.1
2 0 1 82
Log in or sign up to continue


How are you purging this data? SQL? Or by calling a class method such as %DeleteExtent?