Should queries on lower F SKU's fail or just be slower?

[wilson_smyth]

On a low end fabric sku, should the query/job fail or just be very slow?

When fabric was first released I used an F2 Sku for loading and quering some relatively small CSV files and it worked well.
I tried the same today and it fails continually. I ended up trying with a sample csv from contoso, 28kb in size and the results are the same.

Sometimes it will create the table but then be unable to display a preview of the data.
The table also does not show up under the sql endpoint.
Its making fabric unusable for day to day work, even for tiny workloads where a low end sku should be fine.
Appreciate any thoughts and ideas.

[v-jingzhan-msft]

Hi @wilson_smyth 

Have you resolved this issue? If my previous reply was helpful, please consider accepting it as a solution. If you have found other solutions, we would greatly appreciate it if you could share them with us. Thank you!

Additionally, the following issue has been fixed recently, so the first two points in my previous reply should not be a problem for schema enabled lakehouses now. You may check that at your end!

Best Regards,
Jing

Community Support Team

[v-jingzhan-msft · Accepted solution]

Hi @wilson_smyth 

1. "Sometimes it will create the table but then be unable to display a preview of the data."

Did you enable the schema for the lakehouse? If so, currently there is a known issue regarding lakehouses which have enabled schema feature. As a result of this issue, you can't use notebooks to query data from these lakehouse's Delta tables, and you can't preview data in Explorer. Please refer to: 403 Forbidden when reading the tables of the Lakeh... - Microsoft Fabric Community Currently engineers are working on the fix. 

2. The table also does not show up under the sql endpoint.

If you have enabled the schema for the lakehouse, this is a known limitation for lakehouse schemas. Please refer to Public preview limitations in Lakehouse schemas (Preview) - Microsoft Fabric | Microsoft Learn. The specific limitation is "SQL Analytics Endpoint is disabled until a fix is deployed. SQL Analytics Endpoint, Semantic model, and Power BI reporting won't work until then."

3. On a low end fabric sku, should the query/job fail or just be very slow?

Low end Fabric SKUs typically have fewer compute resources. Failures and low performance can occur when there are a large number of concurrent queries or a large amount of query/process data. But 28kb data is usually fine. The problem may lie in the lakehouse schema.

Best Regards,
Jing
If this post helps, please Accept it as Solution to help other members find it. Appreciate your Kudos!