1

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 a 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 another approach?

Peter Mortensen
  • 30,738
  • 21
  • 105
  • 131
Jose Hellginton Cruz
  • 19
  • 1

2 Answers2

0

Try to delete the child objects via IRIS SQL. In this approach, you can see the query plan and maybe add the necessary indices.

Peter Mortensen
  • 30,738
  • 21
  • 105
  • 131
Evgeny Shvarov
  • 468
  • 5
  • 17
0

"purge a single parent and all child tables". As you want to delete the parent too, it should be sufficient to delete just the parent object. By definition, all children should be deleted implicitly. BUT: most of the processing time may be consumed by the maintenance of all related indices.

robert.c.cemper
  • 181
  • 8
  • What do you mean by *"...may take the maintenance of all related indices"*? Do you mean *"...may* ***be taken by*** *the maintenance of all related indices"* (my emphasis)? Or something else? An ideal response would be by [editing (changing) your answer](https://stackoverflow.com/posts/69002882/edit), not here in comments (***without*** "Edit:", "Update:", or similar - the answer should appear as if it was written today). – Peter Mortensen Sep 01 '21 at 09:00
  • changed answer as suggested – robert.c.cemper Sep 01 '21 at 20:18