Suggested by Thomas Sandsør – Completed
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.
Status Details
Thanks for your feedback.
System entities are included in the database storage as indicated in https://docs.microsoft.com/en-us/power-platform/admin/capacity-storage. The Web resource entity will be changed to file capacity instead of database capacity for 2021 Release Wave 1.
-
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
-
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.
-
Agreed, I have database with over 5Gb of data relating to customisations such as these, not customer data
-
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.
-
I find it really unfortunate that you have to pay for storage space that you cannot control in any way. Our database (webresourcebase) doubled overnight, for no apparent reason and we are still at the very beginning of using D365. Furthermore, I do not find it justified to pay for user licenses with which you cannot even run the normal software without worrying about upgrading the database after a few months.
-
Hi, have you noticed the same symptoms within "pure" CDS / Power Apps environments - I mean you do not have any database /environment elements from related Dynamics first party apps? -martti
-
Just had a call with support on this, and the only thing happening was that they were looking into optimizing the indexing of the tables. This reduced my 3 GB of data to 2.9GB. Clearly I was not talking to the correct team to get this fixed. I have another Field Service customer with Sales, and they have 4 GB of Ribbon and WebResource 😒 Will try to rally opp more votes for this, as we all should!
-
Microsoft should fix this issue urgently, it's unfair to ask my customers to pay for these entities.
-
I agree, I think it is totally unfair for Microsoft to be charging us for these tables. In our case we have 4 environments(DEV,QA,UAT and Production) and the Webresourcebase and RibbonClientMetadataBase are taking up 14GB of our 19GB of space
-
It also seems strange that these entities are stored in the database at all. Shouldn't these be moved to the file storage type? Even if they are still included in our storage quota it wouldn't have anywhere near so much impact then.
- 1
- 2
- 3
- ›