Forum Discussion
Helper IVFabric Warehouse Table Size
Hi AJAJ ,
This is expected behavior in Fabric Warehouse and you are not doing anything wrong. The query you found online depends on sys.dm_db_partition_stats, which is a SQL Server DMV and is not supported in Fabric Warehouse. Fabric uses a distributed, serverless SQL engine and only exposes a limited set of system views, so detailed storage allocation information is not available through T SQL. Because of this design, there is currently no supported SQL query that can return the exact size of each table in MB or GB from inside the warehouse.
If you need accurate table storage information, the supported approach is to use the Capacity Metrics app in the Fabric workspace, which shows the actual compressed storage used by warehouse tables. From within SQL, you can still retrieve row counts and column metadata to get a general sense of which tables are larger or smaller, but this should be treated as an estimate only and may not reflect true storage usage due to compression and internal optimizations. In short, the DMV error you are seeing is expected, and using Fabric Capacity Metrics is the correct way to view table sizes today.
Thank you.
Hi AJAJ ,
This is expected behavior in Fabric Warehouse and you are not doing anything wrong. The query you found online depends on sys.dm_db_partition_stats, which is a SQL Server DMV and is not supported in Fabric Warehouse. Fabric uses a distributed, serverless SQL engine and only exposes a limited set of system views, so detailed storage allocation information is not available through T SQL. Because of this design, there is currently no supported SQL query that can return the exact size of each table in MB or GB from inside the warehouse.
If you need accurate table storage information, the supported approach is to use the Capacity Metrics app in the Fabric workspace, which shows the actual compressed storage used by warehouse tables. From within SQL, you can still retrieve row counts and column metadata to get a general sense of which tables are larger or smaller, but this should be treated as an estimate only and may not reflect true storage usage due to compression and internal optimizations. In short, the DMV error you are seeing is expected, and using Fabric Capacity Metrics is the correct way to view table sizes today.
Thank you.
Hi AJAJ ,
I wanted to follow up and see if you had a chance to review the information shared. If you have any further questions or need additional assistance, feel free to reach out.
Thank you.
Hi AJAJ ,
I wanted to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions.
Thank you.