QUESTION::LAKEHOUSE::SQL ENDPOINT::SYSTEM VIEWS

[Element115]

Using a Fabric Trial license.

Why does Microsoft expose a bunch of views in schemas INFORMATION_SCHEMA and sys when these views cannot be queried?  What's the point?

Every single time I try a JOIN on some user object_id to find out how much space one of my tables is using, I get an error message like this one:

SELECT * 
FROM sys.resource_usage;

==>  'resource_usage' is not supported.

Either expose the views if the user can SELECT query them, or don't expose them if the user can't.

[Anonymous]

Hi @Element115 ,

I can reproduce your error.

Some views in sys work fine.

These views are typically part of the system catalog and are intended to provide metadata about database objects.

In the case of a Trial license in Fabric, some views and features may be limited or not fully supported. There may be several reasons for this:

The Trial version may not include all of the functionality found in the full version, which may limit access to certain system views.

Although views are publicly available, query privileges may be restricted to ensure security and data integrity.

If you have any other questions please feel free to contact me.

Best Regards,
Yang
Community Support Team

If there is any post helps, then please consider Accept it as the solution  to help the other members find it more quickly.
If I misunderstand your needs or you still have problems on it, please feel free to let us know. Thanks a lot!

[Element115]

@Anonymous 

1__Are ALL the systeme views, including those in INFORMATION_SCHEMA, available for query if you have a paying SKU?

2__If my user has admin priv, will there still be some restriction?

[Anonymous]

Hi @Element115 ,

Some views are used internally for system operations and development purposes, and they might not be exposed for direct querying regardless of your license type or administrative privileges.

Just because a view is listed doesn’t mean it’s queryable.

Some views are for internal system use and not meant for direct access.

While a paid SKU and admin privileges generally provide broader access, they don’t guarantee visibility of all system views.

Best Regards,
Yang
Community Support Team

If there is any post helps, then please consider Accept it as the solution  to help the other members find it more quickly.
If I misunderstand your needs or you still have problems on it, please feel free to let us know. Thanks a lot!

[Element115]

OK so what is the best way to find the total size in GB of one or more tables if we cannot query system views?

[Anonymous · Accepted solution]

Hi @Element115 ,

Run the following two commands in Notebook to calculate the table size in lakehouse.

The first command contains the table size in byte, my table is smaller, replace the products table with your own when using it.

%%sql
DESCRIBE DETAIL delta.`Tables/products`

The second command converts byte to GB, replacing 3213 with your own after running the first command.

size_in_bytes = 3213

# byte swtich GB
size_in_gb = size_in_bytes / (1024 ** 3)
print(f “Table ‘products’ size: {size_in_gb:.8f} GB”)

Best Regards,
Yang
Community Support Team

If there is any post helps, then please consider Accept it as the solution  to help the other members find it more quickly.
If I misunderstand your needs or you still have problems on it, please feel free to let us know. Thanks a lot!