No more typing reviews! Try our Samantha, our new voice AI agent.

Azure Databricks vs Dremio comparison

 

Comparison Buyer's Guide

Executive Summary

Review summaries and opinions

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Categories and Ranking

Azure Databricks
Ranking in Data Science Platforms
14th
Average Rating
7.8
Reviews Sentiment
4.1
Number of Reviews
6
Ranking in other categories
No ranking in other categories
Dremio
Ranking in Data Science Platforms
10th
Average Rating
8.4
Reviews Sentiment
6.6
Number of Reviews
11
Ranking in other categories
Cloud Data Warehouse (9th)
 

Featured Reviews

SK
Sr. Technical Specialist at Softcell Technologies Limited
Data pipelines have accelerated and support reliable analytics collaboration across teams
From our experience, Azure Databricks could be improved with simpler cluster management and more predictable cost visibility and enhanced native monitoring for large enterprise environments. We would also like richer governance features, better debugging for distributed Spark jobs, and more granular controls for workload optimization over and across multiple teams, which we have at multiple customer environments and within our organization. In day-to-day operations, troubleshooting failed Spark jobs can still be time-consuming, especially in complex distributed workloads. We would like clearer root cause diagnostics and more actionable performance recommendations within Azure Databricks. Better cost optimization insights at the job and cluster level would also help us manage large multiple team environments more efficiently.
Corrr Moray - PeerSpot reviewer
SR BI developer at BRQ Digital Solutions
Has simplified complex data integration workflows and supported consistent reporting across multiple sources
We also have a close relationship with the team that does the Dremio maintenance for the database, like upgrading the versions and they know about some specific problems we had in the past, such as a memory leak. We had a memory leak on some versions, which sometimes stopped the service. Since we are using Dremio installed like a server, not a SaaS solution, many times we need to stop and restart the service to clear all the cache and all that, and this is the thing I should add. I see that many times the new versions of Dremio have not fixed old bugs, and in some new versions, old problems that were previously fixed come back again, so I think the upgrade part could use improvement. I remember using some features in the past, like pivot tables, which proved to be really difficult, but I know this is a fault also for other vendors. Pivoting, transposing, and unpivoting are often not so good. CTEs also many times prove to be not so good, so I think these two main items could be improved significantly if they standardize them.

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"The concept of Azure Databricks is a very good one, especially for the data products concept and idea."
"Azure Databricks gives the capability to handle a lot of big data use cases and machine learning use cases, but machine learning use cases need quite a lot of compute power, and that is where the cost spikes up."
"The best features in Azure Databricks for me are that it's easy to use, flexible, and has fast processing, and you can use multiple data types."
"My pipelines are now significantly faster compared to older ETL tools, as what used to take over 12 to 14 hours to process 2 GB of source data in Synapse Analytics now completes within 5 hours using the Azure Databricks framework for the transformation part, illustrating a substantial improvement in performance."
"Azure Databricks has significantly improved our ability to process data and large data sets, and deliver analytics projects faster for our customers."
"Regarding the learning curve, it is a good technology; it is the first time I am working on a cloud platform, and before that, I have not worked on any data engineering tool that is on cloud, so it is good learning."
"Dremio gives you the ability to create services which do not require additional resources and sterilization."
"Everyone uses Dremio in my company; some use it only for the analytics function."
"Dremio enables you to manage changes more effectively than any other data warehouse platform. There are two things that come into play. One is data lineage. If you are looking at data in Dremio, you may want to know the source and what happened to it along the way or how it may have been transformed in the data pipeline to get to the point where you're consuming it."
"Dremio allows querying the files I have on my block storage or object storage."
"Overall, you can rate it as eight out of ten."
"The most valuable feature of Dremio is it can sit on top of any other data storage, such as Amazon S3, Azure Data Factory, SGFS, or Hive. The memory competition is good. If you are running any kind of materialized view, you'd be running in memory."
"The first feature that stands out for me in Dremio is the federated type of query, which allows the possibility to use multiple endpoints without worrying about writing custom SQL that runs only for SQL Server or for Postgres and Redshift."
"The native error interface has been most valuable."
 

Cons

"From our experience, Azure Databricks could be improved with simpler cluster management and more predictable cost visibility and enhanced native monitoring for large enterprise environments."
"I have given the product a rating of six out of ten just because I do not use all of the functionalities, and I see some direction for improvement as well; also, every product has something to improve, and I have not used many features in this product."
"At this point, I cannot comment on the cost being ideal; it is on the higher side, but in the cloud-based environment, compared to on-premise, it could be far lesser in cost."
"Lower pricing is currently my only focus and I'm still exploring Azure Databricks, so it's too early to say something, but overall, I'm saying that it is the future."
"The only concern is perhaps related to the pricing and cost that Azure Databricks incurs."
"The biggest friction point I have experienced with Azure Databricks is its cost-effectiveness; for projects with less data volume, it is advisable to use Azure Fabric services instead, as Azure Databricks may not be suitable for low volume processing."
"They need to have multiple connectors. Starburst is rich in connectors, however, they are lacking Salesforce connectivity as of today."
"It shows errors sometimes."
"We had a memory leak on some versions, which sometimes stopped the service."
"There are performance issues at times due to our limited experience with Dremio, and the fact that we are running it on single nodes using a community version."
"I cannot use the recursive common table expression (CTE) in Dremio because the support page says it's currently unsupported."
"Dremio takes a long time to execute large queries or the executing of correlated queries or nested queries. Additionally, the solution could improve if we could read data from the streaming pipelines or if it allowed us to create the ETL pipeline directly on top of it, similar to Snowflake."
"Dremio could be improved by making it easier for data cataloging, especially when working with open table formats, as you have to choose a data format and then go into it."
"The community version lacks information or documentation."
 

Pricing and Cost Advice

Information not available
"Dremio is less costly competitively to Snowflake or any other tool."
"Right now the cluster costs approximately $200,000 per month and is based on the volume of data we have."
report
Use our free recommendation engine to learn which Data Science Platforms solutions are best for your needs.
909,725 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
No data available
Financial Services Firm
25%
Computer Software Company
7%
Outsourcing Company
7%
Manufacturing Company
6%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business2
Midsize Enterprise3
Large Enterprise2
By reviewers
Company SizeCount
Small Business2
Midsize Enterprise5
Large Enterprise5
 

Questions from the Community

What is your experience regarding pricing and costs for Azure Databricks?
Regarding the licensing cost of Azure Databricks, it has evolved quite a lot. The compute is the biggest cost, as with any other big data solutions. The storage cost is almost minimal or negligible...
What needs improvement with Azure Databricks?
From our experience, Azure Databricks could be improved with simpler cluster management and more predictable cost visibility and enhanced native monitoring for large enterprise environments. We wou...
What is your primary use case for Azure Databricks?
Azure Databricks is our primary platform for building scalable data engineering and analytics pipelines for enterprise customers. We use it to inject, transform, and process large volumes of struct...
What is your experience regarding pricing and costs for Dremio?
I don't have information about pricing, setup cost, and licensing for Dremio, so I am not entitled to discuss it.
What needs improvement with Dremio?
I wouldn't say there is anything Dremio can be improved on. If I could change something, I would say many developers and programmers, when they are starting to work in this specific field or area, ...
What is your primary use case for Dremio?
I have been using Dremio for a year and a half. My main use case for Dremio is that I am able to access multiple databases and I can easily and quickly connect Dremio with my dashboards. In my rece...
 

Also Known As

No data available
Dremio AWS - BYOL
 

Overview

 

Sample Customers

Information Not Available
UBS, TransUnion, Quantium, Daimler, OVH
Find out what your peers are saying about Azure Databricks vs. Dremio and other solutions. Updated: August 2026.
909,725 professionals have used our research since 2012.