Dynamics Community Forum Thread Details

Dataverse Storage for Finance and Operations database 191.22 of 164 GB used 16,6% over

Dear Microsoft Team,

Please help me out for our Finance and Operations database appears to have exceeded the capacity limit by 16%.

We have questions regarding this :

1. What exactly is the information related to the Finance and Operations database referring to?
As far as we understand, Dynamics 365 Finance and Operations is a SaaS product, where we act solely as users by subscribing to licenses, and all processing—including updates and maintenance—is managed by Microsoft via LCS. However, our server team received a notification from Microsoft regarding "out of database capacity," and it turns out to be related to D365FO.
For your information, we were never advised by our consultant that this Dataverse component requires monitoring or maintenance.

2. From the Dataverse details, we observed two databases related to Finance and Operations: Production and Sandbox.
We’ve attached tables showing which entities are consuming the most space in both environments.
Could you advise us on how to configure, maintain, or shrink these tables Finance and Operations Databases to increase available storage?
And would such actions impact user activities?

We kindly request your support and suggestions on how to resolve this issue effectively.

Thank you for your support.

Best regards,

Thomy MS

Visionet Data Internasional

Lippo Cyber Park

Jl. Boulevard Gajah Mada No.2120, Lippo Village

Kota Tangerang, Banten 15811

P Please consider the environment before printing this email

Categories:

Dynamics 365 general

When you buy Dynamics F&O, you receive a space quota because you purchased the system. You also get additional space allocated with the purchase of each user license. All of this adds up to provide you with a limit of space, up to which you are free to use. After that, Microsoft may charge you per GB, which is about $40 per GB (if I’m not mistaken). If your consultant didn’t tell you this, it’s disappointing – they should have.

Regarding your point on how to clean up, that can be a lengthy discussion. First, you should address the worst offenders (the tables consuming the most space), for example, the top 20 or 30 tables. For each table, a different solution can be applied. If you ask me which solution is best for Table A, I would say that without knowing the table’s name, I can’t provide a solution.

For example, if it’s MR.DB.Fact , the solution is to reset the data mart (just be sure to take a reports backup, just in case).
As another example, if it’s the BatchJobHistory table, you can set up a regular cleanup job that deletes the data.

Depending on the table, the solution may vary. I’d suggest posting a new question for each table, and people can recommend the appropriate treatment.

Quick Links

Leaderboard > Microsoft Dynamics 365 | Integration, Dataverse, and general topics