Hello Community,
I'm bringing up a topic which as been mentioned a few time in this forum about database utilization with no apps in use such as this thread here; however, what is not clear to us is database capacity planning for tables we cannot manage.
We currently have the 1GB database allotment with just the default environment. We've build an app or two and have created a few flows for testing. Since we have just the default environment, we have nothing in use by our users. However, our we have exceeded our database usage allotment by .32GB and file usage by 72MB. Looking at the database tables, WebResourceBase and RibbonClientMetabase are responsible for almost a 1GB of data. I've reviewed the documentation to reduced database usage and I've opened a ticket with Microsoft. Both options have been dead ends.
From what I can see, we have no options for managing these tables. According to Microsoft they are 'core' tables for the environment and they cannot be reduced. We would like create a new environment to start creating Power Apps, however, we don't have available space since 1GB is required.
Since we have exceeded our database allotment with tables we cannot manage, we have a few questions for the community:
- If we purchase additional space whether it's from a new Power Apps licence or additional database allotment, will the current .32GB overage eat into our new allotment? Example: If we purchase 1GB of additional storage, will .32GB be consumed immediately leaving us below the 1GB required to create a new environment?
- Since the tables that are consuming the vast majority of our database allotment (WebResourceBase and RibbonClientMetaBase) and from what I read and experience, these tables will continue to grow exponentially, how can we plan for future database cost for tables we have no control of managing?
Thanks,
