How to find out what contains in the current storage

[bfontana]

Hi guys, 

I've been working in trial license for fabric, and I've installed the Fabric Capacity metric app to analyze the consumption and the storage. 

My storage says is 2.04 GB for billable storage. 

I looked for in the community to analyze which data is taking this value and I got a query to run in the DW to verify the tables sizes. Then I run it in Fabric.

I have only these two warehouse and lakehouse as the screenshots below, and it's saying to me a very short amount in comparison of the Metrics app. 

It is returning me less than 2 MB, and in Metrics app dashboard says 2 GB.

What could it be happen? Would you guys help me to clarify this case?

Thanks

Bruno

[v-pnaroju-msft]

Hi bfontana,

We are following up to check whether you have raised the support ticket.If support ticket is raised kindly share the feedback for the issue raised. If a solution has been provided we kindly request you to share the solution with the community and mark it as the accepted solution, as this will assist others facing similar challenges and benefit the broader community.

Thank you.
 

[v-pnaroju-msft · Accepted solution]

Hi bfontana,

Thank you for your update.

We sincerely apologise for the inconvenience caused.

As the proposed solutions did not resolve the issue, we kindly recommend that you reach out to the Microsoft Support Team through the link provided below. Raising a support ticket will enable you to receive personalised insights related to your account and potential resolutions:
Microsoft Fabric Support and Status | Microsoft Fabric

If you have already taken this step, we request you to share your feedback regarding the issue raised.

Thank you.

[v-pnaroju-msft]

Hi bfontana,

We are following up to see if your query has been resolved. Should you have identified a solution, we kindly request you to share it with the community to assist others facing similar issues.

If our response was helpful, please mark it as the accepted solution and provide kudos, as this helps the broader community.

Thank you.

[bfontana]

Hi @v-pnaroju-msft,

No, I was not able to identify the reason of having this amount of "Current storage" data which I got in Capcity Metrics App. 

Kind regards,

[v-pnaroju-msft]

Hi bfontana,

We wanted to check in regarding your query, as we have not heard back from you. If you have resolved the issue, sharing the solution with the community would be greatly appreciated and could help others encountering similar challenges.

If you found our response useful, kindly mark it as the accepted solution and provide kudos to guide other members.

Thank you.

[v-pnaroju-msft]

Hi bfontana,

Thank you for your update.

Current Storage (GB): Displays the latest storage in GB.

Billable Storage (GB): Displays the billable storage in GB. Please note that soft-deleted data is billed at the same rate as active data.

For a detailed understanding of the storage page in the Microsoft Fabric Capacity Metrics app, which provides capacity storage information, kindly refer to the following link:
Understand the metrics app storage page - Microsoft Fabric | Microsoft Learn

Additionally, please refer to the images below and the link provided for a comprehensive explanation of how OneLake consumes storage and compute resources, along with a detailed example:
OneLake capacity consumption example - Microsoft Fabric | Microsoft Learn

If the proposed solutions does not resolve the issue, we kindly recommend reaching out to the Microsoft Support Team via the link provided below. Raising a support ticket will enable you to receive personalized insights related to your account and potential resolutions:
Microsoft Fabric Support and Status | Microsoft Fabric

If you find our response helpful, we would appreciate it if you could mark it as the accepted solution and provide kudos. This will assist other community members encountering similar queries.

Thank you.

[v-pnaroju-msft]

Hi bfontana,

We have not received a response from you regarding the query and were following up to check if you have found a resolution. If you have identified a solution, we kindly request you to share it with the community, as it may be helpful to others facing a similar issue.

If you find the response helpful, please mark it as the accepted solution and provide kudos, as this will help other members with similar queries.

Thank you.

[bfontana]

Hi @v-pnaroju-msft,

Thank so much for you help. However I was not able to identify the reason of having this amount of storage which I got in Capcity Metrics App. 

The data is less than 2mb based on SQL tables. 

And I don't have too much files on Fabric. I'm using the trial license, I've been working only for 50 days and there is only my user using this workspace. 

Thanks a lot for your patience and support.

Kind regards, 

[v-pnaroju-msft]

Hi bfontana,

OneLake is automatically included with every Fabric tenant and serves as a unified repository for all analytical data. All Fabric data items are inherently configured to store data in OneLake. For instance, when data is stored in a lakehouse or warehouse, it is natively saved in OneLake.

1. At present, Microsoft Fabric does not provide a direct method to view the exact size of individual datasets, dataflows, reports, or models from the workspace settings. However, the following approaches may be helpful:

   a) In Power BI service, large datasets significantly contribute to storage consumption.
   b) If dataflows load substantial amounts of data, they may be indirectly utilising storage.
   c) While reports themselves do not occupy much storage, their associated datasets and snapshots can consume considerable space.

2. Soft-deleted items in Fabric, such as datasets, lakehouse files, or dataflows, continue to incur charges until they are permanently removed. OneLake’s soft delete feature prevents accidental data loss by retaining deleted files for seven days before permanent deletion. Soft-deleted data is billed at the same rate as active data.

   For further details on soft delete, please refer to the following link:
   OneLake Disaster Recovery and Data Protection - Microsoft Fabric | Microsoft Learn

3. For hidden workloads, it is advisable to check for any active dataflows. At times, temporary data generated during transformations may consume storage. Additionally, system logs, dataset snapshots, and query logs could occupy space.

If you find our response helpful, kindly mark it as the accepted solution and provide kudos. This will assist other community members facing similar queries.

Thank you.

[bfontana]

Hi @v-pnaroju-msft, thanks a lot for your answer.

However I still have doubt in to check your suggestions.

How can I check the "datasets, dataflows, reports, and models" sizes? If I go to the Settings option for each file, there is no such information. 

And if you could clearer about your 2nd and 3rd point, how I can find them in Fabric, because I was not able to verify it.

Kind regards,

Bruno

[v-pnaroju-msft]

Hi @bfontana,

We sincerely appreciate your inquiry through the Microsoft Fabric Community Forum.

The Fabric Capacity Metric App measures billable storage, which includes not only the data stored in tables but also additional overheads related to datasets, system usage, reports, models, temporary files, snapshots, logs, indexes, and metadata, all of which contribute to billing.

Kindly follow the steps outlined below to identify the components contributing to the reported storage usage and to address any discrepancies effectively:

1. Examine all assets within the workspace, including datasets, dataflows, reports, and models. Ensure that there are no large or unnecessary items consuming significant storage.
2. Soft-deleted data is billed at the same rate as active data. Verify whether any soft-deleted items are still contributing to storage usage.
3. Check for any unused or hidden workloads within the Fabric environment that might be consuming storage but are not reflected in queries. This may include temporary data from dataflows or transformations, as well as any persistent logs or snapshots.
4. Review storage policies regarding retention settings for historical data, as improper configurations may inflate perceived storage usage.

For further reference, you may find the following links helpful:
Understand the metrics app storage page - Microsoft Fabric | Microsoft Learn
OneLake capacity consumption example - Microsoft Fabric | Microsoft Learn

If you find our response helpful, we kindly request you to mark it as the accepted solution and provide kudos, as this will assist other community members facing similar queries.

Thank you.