Forum Discussion
Longer Refresh Time After Switching from SQL Server to Azure Databricks
- 1 year ago
Hi PrabhakaranM
- SQL Server vs. Databricks Performance:
- Power BI performs better with SQL Server due to full query folding support, while Databricks has limited query folding.
- Databricks Connector Limitations:
- The Databricks connector (via ODBC) adds latency and is less optimized compared to the SQL Server connector.
- Cluster Latency:
- Databricks' distributed cluster adds overhead for job initialization and data fetching, especially for smaller datasets.
- Push Transformations to Databricks: This reduces refresh times significantly.
- Optimize Databricks: Use indexes, cache tables, and optimize queries in Databricks SQL.
- Cluster Settings: Ensure proper cluster configuration and enable SQL caching.
- Parallel Execution: Minimize dependencies between tables in Power BI to enable parallel queries.
Did I answer your question? Mark my post as a solution, this will help others!
If my response(s) assisted you in any way, don't forget to drop me a "Kudos" 🙂Kind Regards,
Poojara
Data Analyst | MSBI Developer | Power BI Consultant
Consider Subscribing my YouTube for Beginners/Advance Concepts: https://youtube.com/@biconcepts?si=04iw9SYI2HN80HKS - SQL Server vs. Databricks Performance:
PrabhakaranM As we haven’t heard back from you, we wanted to kindly follow up to check if the solution provided by our super users for your issue worked? or let us know if you need any further assistance here?
Thanks,
Prashanth Are
MS Fabric community support
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly and give Kudos if helped you resolve your query