Dremio AWS - BYOL

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 recent project, my databases are full of information about our insurance operation, and I monitor my KPIs by connecting Dremio to my dashboards. I have multiple KPIs that I have to stay tuned to, and I need to access that very quickly and in an easy way, which is how Dremio helps me.

About my use case with Dremio, I find databases that I don't know very much about, and in that web environment of Dremio, I am able to scroll and navigate through the databases by searching for an example or a column name, so it is much easier to navigate through with that kind of help.

The best features Dremio offers, in my opinion, probably include the web environment.

What stands out to me about the web environment is both the interface and the speed; it helps a lot.

In terms of features, querying is very easy and the integration with multiple dashboards is amazing.

Dremio has positively impacted my organization as nowadays we are connected to multiple databases from multiple environments, multiple APIs, and applications, and Dremio organizes everything in an amazing way for me.

A specific outcome that shows how Dremio has helped my organization is definitely better data access.

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.

I have been working with data analysis for five years now.

In my experience, Dremio is stable.

I have never had any experience scaling up or down with Dremio.

I have never tried to reach customer support.

I didn't get to choose the solution I used before Dremio, which was SQL Server  from Microsoft. Nowadays I see that SQL Server solution is much more simple, and Dremio helps me a lot to move beyond that simplicity.

My advice for others looking into using Dremio is to explore the web environment and stay sharp with the ODBC connectors and drivers, as that is very important. I would rate this product a 9.

As a BI developer, my main use case for Dremio  involves registering data zones and also doing inquiries, views, and making it persistent to use on BI tools, like Tableau reports. In a project, we create data zones, typically one that we have in our company to receive files. After doing the ingestion inside Dremio , what we do is set up permissions, and after setting up the permissions, the refresh session allows us to go over and start building the views and all those things to be possible to connect via JDBC driver and consume on Dremio dashboard.

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. We build a SQL on Dremio standard, and then Dremio goes over and rewrites the whole lineage to make it possible to use multiple sources of data.

The feature impacts our daily work by reducing complexity because we don't need to worry about where the data comes from. We are slightly migrating to Snowflake , so Dremio is currently being replaced because Snowflake  is a more robust platform, but we are kind of happy with the work Dremio does.

I think the reduction of complexity is a positive impact that Dremio has had on my organization. The main thing is that it is a place where you can write down simple SQLs and see the lineage, the way it integrates together; this is the best part of it.

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.

I have been using Dremio for approximately three years, since January of 2022.

We had a memory leak on some versions, which sometimes stopped the service. Many times, we need to stop and restart the service to clear all the cache and all that. I rate Dremio a nine in terms of stability. I think it is stable, but we need to restart it many times, and we need to monitor it regularly.

Dremio's scalability can handle growing data and user demands easily.

We have had to reach out for customer support many times, and they respond, so they are pretty supportive about some long-term issues. Many times it's with vendors where there is a missing feature or ongoing problem that they say will be fixed in the next release, but this happens not only with Dremio but with almost every vendor we have.

We haven't previously used a different solution before Dremio. Snowflake is the new solution we are currently using to replace Dremio.

I cannot share the exact metric itself, but Dremio surely saves time, reduces costs, and all those things because we don't have to worry so much about the infrastructure to make the different tools communicate. Dremio was a solution that made it possible for us to have different data sources with only one registration on our data lake.

I don't have information about pricing, setup cost, and licensing for Dremio, so I am not entitled to discuss it.

I probably don't remember all the options we evaluated, but we talked a lot about Databricks  and Redshift, and Dremio was the best choice. Also, we don't use Tableau Prep because we use Dremio, which is an important thing.

My advice to others looking into using Dremio is that it is a great tool because it keeps all your efforts together. It's a good thing to have if you want to have a unified catalog or metadata or something like this, so this is certainly a good tool to consider. I would rate this review an eight out of ten overall.

I have been using Dremio  on and off as a data warehouse for the past three years.

My main use case for Dremio  is that we use it as a logical data warehouse where we use Dremio with VDSs as an alternative to AWS Glue  or Apache Hive . As we are working with our ETL at the end of all of it, after the data types and everything have been cast, we make that available on Dremio as VDS and then we move on to our further data warehousing schemes within Dremio.

We use Dremio enterprise-wide now, and the key use case has been reducing our costs when it comes to data storage.

Our main use case for Dremio is as a data warehouse, and the challenge that it helped us solve is that physical data warehouses such as Redshift have storage and hardware upscaling conflicts. Dremio helps us decouple those and lets us catalog more. We can manage everything under one system.

The best features Dremio offers include having a single system where we can manage all of our data cataloging and visualization or virtualization.

The interface is a plus over the traditional warehousing solutions, which makes it easier to work with Dremio compared to other solutions I've used.

Having everything under one system and an easier-to-work-with interface, along with having API integrations, adds significant value to working with Dremio.

Dremio has positively impacted my organization by helping us create a single source of truth, a singular data warehouse where we can have access to all of the data sets. The fact that Dremio has a clear role-based access management system helps us significantly, as we can have roles segregating all of the data, while users with the appropriate roles can access everything.

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.

I have been working in my current field for five years.

In my experience, Dremio is reasonably stable.

I haven't pushed Dremio's scalability to its limit, so I cannot provide detailed information about that.

I haven't had the need to interact with Dremio's support team yet.

Before Dremio, we used Hive  and AWS Glue , and we wanted to shift to an open-source version that is newer than Hive and provides flexibility in moving between cloud and on-premises.

We evaluated other options before choosing Dremio, including Presto  and Trino, but we did not find reasonable advantages to using them.

I don't have the appropriate information regarding pricing, setup cost, and licensing as that is managed by a different team.

I cannot share return on investment information from using Dremio.

We evaluated other options before choosing Dremio, including Presto  and Trino, but we did not find reasonable advantages to using them.

I would advise others looking into using Dremio to study the tool beforehand. Dremio has several different offerings, and the best way to get into it is to use the open-source on-premises version to experiment with it. To extract the complete power of the platform, organizations should educate themselves with the complete information and compare it with other solutions since a single solution cannot fit everywhere. Educating the team before adopting a technology is better than just adopting a suggested package. I rate Dremio 8 out of 10.