EventCUD is a table normally used for handling change based and due dates alerts in Dynamics 365 F&O.  The details of this process is available here : https://learn.microsoft.com/en-us/dynamics365/fin-ops-core/fin-ops/get-started/alerts-managing

But up until 10.0.38, there was a bug, that could led to orphan “triggers”

The fix from Microsoft does not fix orphan triggers originating from before this fix, so you have to open a support ticket to get it fixed, and also to get the EventCUD table truncated

The way you can identify if you are affected by orphan triggers is to open the D365 with the following URL parameters &mi=SysTableBrowser&Tablename=EventCUD. Then look for lines with old created dates:

You should also look for CUDTableId’s not matching your table ID’s on the alerts and database logging.

If you have a “full “ EventCUD and “orphan triggers”, and clean them up, you should experience some performance gains.

And last comment.  Please avoid logging and alerting on high frequency transaction tables.  Take care 😊