Cross datawarehouse queries

[sana_ali84]

 Is doing cross data warehouse queries an expensive operation in terms of cost and performance?

[Anonymous]

Hi @sana_ali84 ,

We haven’t received an update from you in some time. Could you please let us know if the issue has been resolved?
If you still require support, please let us know, we are happy to assist you.

Thank you.

[Anonymous]

Hi @sana_ali84 ,

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.

[Anonymous]

Hi @sana_ali84 ,

I wanted to follow up on our previous suggestions. We would like to hear back from you to ensure we can assist you further.

Thank you.

[Anonymous · Accepted solution]

Hi @sana_ali84 ,
Thank you for reaching out to the Microsoft fabric community forum.

Running queries across multiple warehouses typically uses more resources than querying within a single warehouse, which can affect both performance and cost. This is due to factors like extra data movement, distributed joins, and coordination between compute engines, all of which can increase query latency and resource consumption.

Because of this, total capacity usage and costs may rise. To address this, consider optimizing queries by applying filters early, reducing data movement, and, where possible, consolidating commonly joined data into one warehouse. Using Fabric’s diagnostics tools can also help you monitor and improve query performance and efficiency.

Hope this helps. Please reach out for further assistance.

Thank you.

[sana_ali84]

Yes, thanks for the information. This is usefule information