35
Running a organization with D365 CE + Portals and Marketing. The webResourceBase and ribbonClientMetatdataBase consume more than 3 gb of data, and this is something we can't control!

The CRM solution is pretty vanilla without custom ribbon and only 1 custom javascript.

Tables like this should not count in our complete storage.
Category: General
STATUS DETAILS
New

Comments

T

We have noticed this at 3 customer sites now. The "webresourcebase" and "ribbonclientmetadatabase" tables have grown to consume over 1/3 of their entire storage space. We cannot ask customers to "pay for more storage space" when this much is consumed by system tables they have no control over.

Category: General

T

Agreed, I have database with over 5Gb of data relating to customisations such as these, not customer data

Category: General

T

I totally agree. It should not be allocated to any storage. When creating a new environment it requires 3-4GB data storage, not just 1GB as the licencing says.

Category: General

T

This is not only related to a Marketing and Portal environment. Any D365 CE App added to the CDS means huge amounts of space are taken up immediately with no way for us to control it.

The type of space these necessary files consume is allocated to our Data allowance which is the most expensive type of storage. We have heard directly from Microsoft support that there is no way to reduce the size of them and they just continually get bigger and bigger. These tables should be allocated to the Files data storage type. They are tables that Microsoft require to run the application, nothing to do with our data usage. The fact that we cannot reduce them in any way makes in incredibly unfair that we must pay in this way.

Main culprits are:
-webresourcebase
-ribbonclientmetadatabase
-runtimedependancybase
-systemfrombase

Category: General