Dynamics Community Forum Thread Details

Best Practices for Data Cleanup and Capacity Management in D365 SCM

Hello community,

We are currently facing an unexpected database capacity issue and would appreciate advice from organizations with experience in managing large D365 Finance & Operations environments.

Until 30 July 2026, our tenant had approximately 2 TB of available database capacity. We have 4 Environments with a total database consumption of around 690 GB.

Unexpectedly, Microsoft reduced our available database capacity from approximately 2 TB to 705 GB. We are currently investigating the reason together with Microsoft, as we do not yet understand what caused this change.

As a result, we are now operating very close to our capacity limit:

Available database capacity: 705 GB
Current database consumption: ~690 GB

This leaves only a small amount of remaining capacity and requires us to start identifying cleanup opportunities.

We are looking for practical recommendations to:

Reduce database size where possible
Implement sustainable cleanup processes
Establish retention rules
Prevent future capacity issues

Questions

Which data areas or entities do you clean up regularly to reduce database growth?
Which standard cleanup jobs provide the biggest storage savings?
Are there Microsoft-recommended cleanup routines for large F&O databases?
How do you identify the largest tables and the fastest-growing data areas?
Which retention policies have worked well in your organization?
Are there any commonly overlooked tables that consume significant storage?
Has anyone experienced a similar reduction in available capacity, and if so, what was the root cause?

Categories:

Dynamics 365 Supply Chain Management

The chart is quite interesting because it looks like the issue may not simply be database growth. Your entitled capacity was around 2.1 TB on June 29 and then dropped to 705 GB on July 30, while your actual database consumption is around 690 GB.

I’d first focus on understanding what caused that entitlement change with Microsoft before doing any major cleanup. It would be useful to confirm whether there was a change related to licensing, subscription/tenant configuration, or the capacity entitlement itself.

For the cleanup side, I’d start by identifying the largest and fastest-growing tables rather than deleting data broadly. Reviewing batch history, database logs, workflow history, document attachments, and other historical data can often highlight areas where retention policies can be applied.

For a long-term solution, I’d recommend setting retention rules based on business and regulatory requirements and monitoring database growth regularly. That way, unusual growth can be identified before the environment gets close to its limit.

It would also be interesting to hear from others who have seen a similar sudden change in entitled capacity, because the drop from ~2.1 TB to 705 GB seems to be the key issue here.

Quick Links

Leaderboard > Supply chain | Supply Chain Management, Commerce