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.
-
I am going through this same problem.
-
As somebody mentioned here. It's unfair from MS to charge us and our clients for system tables in Dynamics. I can understand part of webResourceBase, but only resources not related to standard functionalities. I totally don't understand ribbonClientMetatdataBase which is definitely out of our control.
-
Our top two tables in storage capacity: WebResourceBase RibbonClientMetadataBase
-
This had caused a major delay for us, we don't use CRM, however as the MS system tables exceeded the 1GB allocated for our old Default instance, I was unable to create a new Prod instance. I had to log a support case, have it escalated Premier Support, engage our TAM to had sort this. It is far to complicated, takes too long, and there is such little advise about what to do with this. Please exclude the system tables from the quota so that the product is even partially useable.
-
Same here, I've created a new sandbox instance with the Sales Enterprise app only and database usage was 1.0 GB. 24h later, without doing anything to this instance except system configurations (date and time formats, deactivation of Skype integration, etc... only admin stuff), the database usage was already 2.11 GB! This is not acceptable!
-
Seeing the same thing here. WebResourceBase in particular seems to keep growing. I've gone through all the tips to reduce storage usage and none have any effect.
-
This is definitely a problem. Perhaps the reason for the new pricing model is that MSFT realized this was going to happen. There also seems to be some problem with accumulation of unused web resources. We have a dev environment that has been around for 6 months or so and the web resource base table is at 1.9GB; the preprod environment just created with all the same solutions deployed has web resource base at 1.1GB. MSFT should look at using a CDN to deliver web resource content instead of sticking BLOBs in a database.
-
Shocked to see GB of an environment grow while customer is not adding any data 💸
-
Totally agree with this, our sandbox/uat environments are increasing in the same fashion. We are having to delete non-essential environments just to keep under storage quotas causing development practices and processes to be hindered.
-
Totally agree with the above. Customers should not be made to pay for something that is beyond their control. I realised the 'Webresourcebase', 'SystemFormBase' and 'ribbonclientmetadatabase' gets much bigger after each major upgrade (i.e. the yearly Wave 1 and 2). So here we are trying all sorts of measures to reduce the storage only to have Microsoft adding new solutions and inflating our storage again. These tables should be excluded from the storage quota.
- ‹
- 1
- 2
- 3
- ›