Views:

Applies to Product -Dynamics 365 Lifecycle Services


What’s happening?
Customers need to perform cleanup activities for specific database tables (e.g., EVENTCUD, AXDB.BIINCREMENTALTABLEMODIFICATIONS) in production environments due to excessive data growth impacting database capacity.


Reason:
The underlying cause for the need to truncate these tables is the accumulation of excessive data, which has led to significant storage consumption. In some cases, alert setups or batch jobs may also contribute to the continuous growth of these tables.


Resolution:

  1. Preparation Steps:
  2. Ensure that any unused rules are deleted from the UI by navigating to Modules > System Administration > SetUp > Alert Rules. This prevents the creation of new rows in the EventCUD table for triggered changes.
  3. Put any Change Based Alerts Batch Job and/or Due Date Alerts Batch Job (if they exist) in a withhold state prior to the cleanup activity.
  4. Truncation Process:
  5. Customers can truncate the specified tables themselves using X++ scripts. Documentation for running custom scripts in production can be found at: Run custom X++ scripts with zero downtime.
  6. Confirm that the truncation has been executed successfully and monitor for any further issues.
  7. Follow-Up:
  8. After the truncation, confirm with the support team if there are any pending queries or issues related to the cleanup activity. If everything is resolved, the case can be archived.
  9. If Issues Persist:
  10. If the truncation fails or if there are any errors (e.g., lock request time out), ensure that all relevant batch jobs are paused and reschedule the truncation activity during a designated downtime window.