Partitioning and Clustering in Azure Dataware and Lake house For GCP to Azure Migration

[iamabhaykmr]

Hi everyone,

In BigQuery (GCP) we have partitioning and clustering, which often makes complex analytical queries run much faster by reducing the amount of data scanned.

I’m exploring Microsoft Fabric and had a few questions:

1. Does Fabric have an equivalent concept to BigQuery partitioning/clustering?

2. I tried partitioning in a Fabric Lakehouse (Delta tables), but the performance wasn’t comparable to BigQuery for the same query pattern. Are there Fabric-specific best practices I might be missing (file sizing, OPTIMIZE, Z-ORDER, V-Order, etc.)?

3. I also couldn’t find a clear, official approach for partitioning in Fabric Data Warehouse. Is partitioning supported there, or is there another recommended mechanism?

If anyone has implemented a partitioning/clustering strategy in Fabric Lakehouse or Fabric Warehouse to improve query performance, I’d love to hear what worked (and what didn’t). Any references or examples would be really helpful.

Thanks in advance!

[v-aatheeque]

Hi @iamabhaykmr 

Following up to confirm if the earlier responses addressed your query. If not, please share your questions and we’ll assist further.

[v-aatheeque]

Hi @iamabhaykmr 

We wanted to follow up to check if you’ve had an opportunity to review the previous responses. If you require further assistance, please don’t hesitate to let us know.

[AndyDDC]

For Fabric Warehouse there is no partitioning available, but there is clustering: Data Clustering in Fabric Data Warehouse - Microsoft Fabric | Microsoft Learn

[v-aatheeque · Accepted solution]

Hi @iamabhaykmr 
Thanks for reaching out to  Microsoft Fabric Community Forum.

Fabric doesn’t use partitioning/clustering in the same way as BigQuery, but similar performance optimizations are available through Lakehouse partitioning, file compaction (OPTIMIZE), and data layout techniques like Z-Order / V-Order.

For Fabric Data Warehouse, user-managed partitioning isn’t exposed like in BigQuery. The recommended approach is to optimize large tables in the Lakehouse and then query or materialize curated data into the Warehouse.

You can also refer to similar solved threads and official Fabric performance guidance for best practices around Delta table optimization and Warehouse performance tuning.

Reference : Solved: V-Order & Z-Order - Microsoft Fabric Community
Solved: OPTIMIZE VORDER for partitioned tables - Microsoft Fabric Community
Solved: Re: Partitioning Strategy - Microsoft Fabric Community

Hope this helps !!

Thank You.