web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

News and Announcements icon
Community site session details

Community site session details

Session Id :
Finance | Project Operations, Human Resources, ...
Unanswered

Scalability Question in D365FO

(0) ShareShare
ReportReport
Posted on by 351

We are wondering best practices for dealing with dataverse space issue.  Our database is at 85% capacity and were thinking about adding space.  It seems like there are two scenarios for taking care of this.  One is adding another D365 license which gives ‘x’ amount of space and the second is buying 100GB (just as a number for this scenario).  Going the route of buying more space seems hugely more expensive than an additional license.  Ultimately the end game is to double up on Dev and UAT boxes which is why we would run out of space.  What would be best practice if we wanted to keep all data, history, log info for each of the environments (dev, uat and prod)?

Categories:
I have the same question (0)
  • Diego Mancassola Profile Picture
    914 Super User 2026 Season 2 on at

    Hi, this is becoming a very common discussed topic, especially now that customers are starting to receive capacity-overage notifications.

    The first priority should be keeping production as clean and efficient as possible by using Microsoft’s official cleanup routines, especially for batch history, database logs, Data Management staging data and other log tables. Microsoft provides a complete overview here: Cleanup routines in Dynamics 365 Finance and Supply Chain Management.

    For non-production environments, a recent full copy of production can be useful for UAT and debugging, but DEV environments rarely need the complete transaction history. Transaction-less copies should therefore be considered to reduce storage consumption. A date-based copy that retains only a defined period of transactions would be ideal and is often discussed, but not yet implemented i know, although the standard transaction-less copy currently removes transactions based on table groups rather than a date range.

    Historical production data should also be evaluated for archiving through Dataverse long-term retention, which provides a more cost-efficient location for inactive data: Archive Finance and Operations data with Dataverse.

    Only after applying cleanup, archiving and a purpose-based environment strategy would I consider purchasing additional capacity. Adding licenses solely to obtain storage may appear cheaper, but the actual entitlement and licensing conditions should first be verified with Microsoft or your licensing partner.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Season of Sharing Community Challenge Winners!

Congratulations to our community stars!

Women in Power Builds Momentum

Expanding mentorship, skilling, and AI innovation

Congratulations to the July Top 10 Community Leaders

These are the community rock stars!

Leaderboard > Finance | Project Operations, Human Resources, AX, GP, SL

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 305 Super User 2026 Season 2

#2
Martin Dráb Profile Picture

Martin Dráb 281 Most Valuable Professional

#3
Anton Venter Profile Picture

Anton Venter 266 Super User 2026 Season 2

Last 30 days Overall leaderboard

Product updates

Dynamics 365 release plans