Data Analyst at a insurance company with 501-1,000 employees
Real User
Top 10
Oct 30, 2025
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, are much more used to SQL Server, the Microsoft way of querying, and Dremio has some features that are different when we are talking about the syntax of coding, so I would improve that.
Senior Consultant - Data Analytics at a comms service provider with 201-500 employees
Real User
Top 5
Oct 21, 2025
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. With the Dremio software version that we're using, all that requires a learning curve, and only when you go to the premium cloud version do you get Dremio Arctic. It should be easier to get Arctic or an open-source version of Arctic onto the software version so that development teams can experiment with it.
They need to have multiple connectors. Starburst is rich in connectors, however, they are lacking Salesforce connectivity as of today. They don't have Salesforce connectivity. However, Starburst does. Starburst has all these capabilities. Dremio has only 15 to 20 connectors, however, Starburst comes with around 50 now.
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. We face certain issues when connecting Dremio to MongoDB, especially with max values, which seem to be inconsistent in Dremio. Additionally, licensing is quite expensive, and we feel the need for more flexible schema capabilities, especially in embedding JSON from MongoDB.
Security Data Engineer at a pharma/biotech company with 5,001-10,000 employees
Real User
Jan 16, 2024
Dremio's interface is good, but it has a few limitations. I cannot do a lot of things with ANSI SQL or basic SQL. I cannot use the recursive common table expression (CTE) in Dremio because the support page says it's currently unsupported. The use case I am working on requires building trees and hierarchical structures. Most of the time, it requires complex nested data structures to be made simpler for end users. It would be good if Dremio could provide a way to create trees just like Oracle does using commands like CONNECT BY and NO CYCLE. You can use a few languages to simplify complicated JSON and XML. It would be very helpful if Dremio could provide a solution to simplify building trees and building meaningful data from complex data.
Sr Manager at a transportation company with 10,001+ employees
Real User
Dec 6, 2023
We've faced a challenge with integrating Dremio and Databricks, specifically regarding authentication. It is not shaking hands very easily. We had to set up two different VMs and execute them in a different manner and integrate them.
They have an automated tool for building SQL queries, so you don't need to know SQL. That interface works, but it could be more efficient in terms of the SQL generated from those things. It's going through some growing pains. There is so much value in tools like these for people with no SQL experience. Over time, Dermio will make these capabilities more accessible to users who aren't database people.
One of the areas of improvement is that a table does not break and shows errors. When the 23rd version was released, I had to contact Dermio customer support, and they suggested I update the database to run the table. Sometimes you face common errors like tables running strictly and taking time to run. I think Dermio can improve this part. An additional feature can be a feature where everyone can see the tables.
Dremio doesn't support the Delta connector. Dremio writes the IT support for Delta, but the support isn't great. There is definitely room for improvement. The community version lacks information or documentation. If you want to create a more dynamic scaling policy for your cluster, it's always a problem because you need an additional custom code to be sure that Dremio shuts down gracefully and does not get interrupted. The support of the Delta I/O connector could be improved because the current support is very basic and the performance isn't great.
Dremio offers a comprehensive platform for data warehousing and data engineering, integrating seamlessly with data storage systems like Amazon S3 and Azure. Its main features include scalability, query federation, and data reflection.Dremio's core strength lies in its ability to function as a robust data lake query engine and data warehousing solution. It facilitates the creation of complex queries with ease, thanks to its support for Apache Airflow and query federation across endpoints....
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, are much more used to SQL Server, the Microsoft way of querying, and Dremio has some features that are different when we are talking about the syntax of coding, so I would improve that.
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. With the Dremio software version that we're using, all that requires a learning curve, and only when you go to the premium cloud version do you get Dremio Arctic. It should be easier to get Arctic or an open-source version of Arctic onto the software version so that development teams can experiment with it.
They need to have multiple connectors. Starburst is rich in connectors, however, they are lacking Salesforce connectivity as of today. They don't have Salesforce connectivity. However, Starburst does. Starburst has all these capabilities. Dremio has only 15 to 20 connectors, however, Starburst comes with around 50 now.
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. We face certain issues when connecting Dremio to MongoDB, especially with max values, which seem to be inconsistent in Dremio. Additionally, licensing is quite expensive, and we feel the need for more flexible schema capabilities, especially in embedding JSON from MongoDB.
Dremio's interface is good, but it has a few limitations. I cannot do a lot of things with ANSI SQL or basic SQL. I cannot use the recursive common table expression (CTE) in Dremio because the support page says it's currently unsupported. The use case I am working on requires building trees and hierarchical structures. Most of the time, it requires complex nested data structures to be made simpler for end users. It would be good if Dremio could provide a way to create trees just like Oracle does using commands like CONNECT BY and NO CYCLE. You can use a few languages to simplify complicated JSON and XML. It would be very helpful if Dremio could provide a solution to simplify building trees and building meaningful data from complex data.
We've faced a challenge with integrating Dremio and Databricks, specifically regarding authentication. It is not shaking hands very easily. We had to set up two different VMs and execute them in a different manner and integrate them.
They have an automated tool for building SQL queries, so you don't need to know SQL. That interface works, but it could be more efficient in terms of the SQL generated from those things. It's going through some growing pains. There is so much value in tools like these for people with no SQL experience. Over time, Dermio will make these capabilities more accessible to users who aren't database people.
One of the areas of improvement is that a table does not break and shows errors. When the 23rd version was released, I had to contact Dermio customer support, and they suggested I update the database to run the table. Sometimes you face common errors like tables running strictly and taking time to run. I think Dermio can improve this part. An additional feature can be a feature where everyone can see the tables.
Dremio doesn't support the Delta connector. Dremio writes the IT support for Delta, but the support isn't great. There is definitely room for improvement. The community version lacks information or documentation. If you want to create a more dynamic scaling policy for your cluster, it's always a problem because you need an additional custom code to be sure that Dremio shuts down gracefully and does not get interrupted. The support of the Delta I/O connector could be improved because the current support is very basic and the performance isn't great.