Databricks limitations and workaround

Question

Hi friends what are the limitations of azure Databricks what is the workaround to this limitations

Answer 1

Hello @Anshal ,

Welcome to the MS Q&A platform.

When you say "Databricks Limitations", are you looking for any specific features when compared to Synapse analytics?

Here are some of the limitations of Databricks when compared to the synapse. The workaround is "Synapse analytics"

Databricks leverages the Delta Lakehouse paradigm offering core BI functionalities but a full SQL traditional BI data warehouse experience.

Doesn’t provide a full T-SQL experience (Spark SQL)

Databricks is not a data warehouse tool but rather a spark-based tool

To query the data lake, we need to mount the data lake to data bricks for any python, scala, or R operations

Databricks is more fit data scientists(for BI developers synapse is more suitable as Synapse is built on SQL engine)

Databricks is built on Spark Engine.

You can't use Databricks for full relational data models(as a traditional Dataware house)

For reporting and self-service BI synapse is preferred.

You can't use Power BI directly from Databricks.

Reference documents:

https://learn.microsoft.com/en-us/azure/databricks/
https://www.element61.be/en/resource/when-use-azure-synapse-analytics-andor-azure-databricks
https://learn.microsoft.com/en-us/azure/synapse-analytics/

In case if you are looking for something else, please let us know.

------------------------------

• Please don't forget to click on or upvote button whenever the information provided helps you. Original posters help the community find answers faster by identifying the correct answer. Here is how
• Want a reminder to come back and check responses? Here is how to subscribe to a notification
• If you are interested in joining the VM program and help shape the future of Q&A: Here is how you can be part of Q&A Volunteer Moderators