I have been investigating how storage is reported and billed, and discovered that the Fabric Capacity Metrics report's 'Current Storage (GB)' figure is inconsistent with the same value reported elsewhere in the service. A week ago, I truncated all tables in warehouses in a given workspace. There are no other storage items in that workspace. A week later and after several refreshes, we are still getting a value of 38.72GB in current storage for that workspace:
Looking at that workspace's storage count, we see there's actually 0MB reported:
Using a notebook to retrieve warehouse file sizes reveals all warehouses in the workspace with a file size of 0:
So why is the metrics capacity app returning a value (which has slightly dropped since the truncation)? Can we trust onelake storage billing if this isn't accurate?
1 Comment
JoshTAdvocate III
Somehow the current storage figure has gone up by ~ 50MB the following day! I can confirm no processes have been run that have populated any of the storage items in that workspace, and all still remain at 0GB