Cleaning up Update Set Logs [sys_update_set_log]

[Mark Roethof]

Hi all,

While diving into Database Footprint, Clone Definitions, etc. I stumbled on table "Update Set Logs" [sys_update_set_log]. A table which can easily consist of miljons and miljons of records. At one of my customers for example tens of miljons of records, even from more than 10 years ago.

Out-of-the-box there's no Table Cleaner on this table, or Scheduled Job, etc.. Wondering though, what do others do regarding this table? For example did you create a Table Cleaner yourselves, with a date of 90 days or something? Or is it a big NO NO to cleanup this table? And would you exclude this table with System Clones?

Kind regards,
Mark

[JeffPatt]

I've just noticed the same after cloneovers on my non-prods, also keen to see what the community thinks.

Looking at the logs themselves they seem pretty detached and grow outdated quickly. I can't see a use for logs from 2 years ago, in an area that has since been overwritten by other changes.