We have an almost blank D365 Sales org we use for demos. It has steadily grown in size over the last 12 months. Now that we are allocated a certain amount of database space, rather than paying by the environment, this is becoming more of an issue.
When you create a new D365 Sales app deployment, it sits at about 1GB. Sometimes, things happen that make the space jump massively. For instance on 2nd Feb this year the ribbonClientMetatdataBase table almost doubled overnight for no apparent reason from 600MB to 1+GB. The webResourceBase table is over 2GB!
If you go over you limit you now must pay £30 per GB per month for this database storage. These are Microsoft controlled tables which the app relies on to function. There is nothing we can do about their size and they just seem to grow and grow and grow. I think these tables should be excluded from our database allowances. We are paying on a per user per month basis for the app anyway which should cover these essential tables. It is very unfair to make us pay twice. Either that or we need to be given tools to allow us to reduce the size of these talbes. I mean really, what could possible be stored about ribbon meta data that takes up more than 1GB in a database? It's crazy!
I have these problems in about 5 different environments in the same tenant. Basically blank D365 apps which take up over 5GB each and they didn't start out that way. They have just grown over time with nothing we can do about it. I have tried all the usual steps of cleaning them up by running bulk delete jobs etc.
