What needs improvement with Denodo?

As we are still in the initial phase, it's difficult to identify weaknesses. However, ensuring data caching is up to date is critical. While AI and ML integration is present, understanding its implementation better could be beneficial.

I am still waiting for Denodo to support vector databases. Currently, Denodo does not provide a vector database, which my customers build on their own to use AI functionalities.

They need to invest more in the optimization engine. It will be a fantastic tool for them to enhance automation and improve the GUI interface, especially for Integration, as some tools are still not fully integrated, such as Iceberg. Batch processing is very good but not yet fully integrated. Therefore, they should focus on improving the GUI interface, enhancing cloud capabilities, and integrating modern technologies like Iceberg. Additionally, they should continue refining the optimization engine itself.

Data transformation must be improved. Denodo is not the best tool for data transformation.

Sometimes, Windows-related functions do not work properly in Denodo. The analytic functions in SQL do not work properly. The aforementioned area in the product needs to be taken care of for improvements.

The solution is slow when there are many virtualization layers. The solution is also slow when we connect the on-premise solution with the one on the cloud through a network gateway.

There are a few cosmetic changes that would make Denodo better, including offering holistic governance. It would be beneficial if you could see what inquiries are going around Denodo on the remote system, including who has logged in and which one is using which part of the deviant spaces. Denodo has provided several modules with their scheduler that also have room for improvement. When thinking about future releases, Denodo should consider their platform availability because our administrator has seen some challenges in this regard. It requires some optimization on the developer side as well. Denodo would benefit from having a more user-friendly view. It would be good if the solution provided a much-needed cellular platform.

I would like it if we could pull the data model or export the data model because Denodo has, based on how you build, something called associations. The data model gets very confusing when you go look at it. It depends on how you define it, but it's really huge. I wish there was a way to export it into Visio. It could be that they already have a way to do it, and I don't know, but it would be much easier for the architects and even for the developers to look at it than scrunching it into the screen and expanding every small portion of it. If there was an easy way to export the Denodo model into another modeling tool and view it, it would be great. We are also trying to use Denodo as a cataloging tool so that we can put proper definitions, and once they are made available to our business users, it becomes easy. Using the Denodo layer, we can write queries to pull data. There is a virtualization layer. So, we can interact with it just like any other database. If there was a way to write a query and make my query public to other users so that they don't have to come in and write their queries, it would be great. There should be reusability of something that I did. For example, if I'm working in the healthcare industry and I want to get a view of the patient count for the whole year, I should be able to write a query and make it public so that whoever wants to use it can use that query instead of creating the same query again.

Denodo has some difficulty supporting large numbers of records. Its error reporting is also unreliable and doesn't give clear information on the problem. We've also recently had an issue with roles getting deleted.

Tasks such as conversion of a date format or conversion of a number format that can be done in a very easy way in different languages, like SQL or Oracle, are not so easy to do in Denodo. For example, if you want to convert a date from one format to another, in Oracle it's pretty easy; in Denodo, however, it requires so many lines of code. Simple things that can be done very quickly in other database languages require more lines of code in Denodo. The scheduler UI in 8.0 is not as good as that in 7.0. We have thousands of jobs, and if you search one job, get it, and click on it, when you come back, your search will be gone. You have to do your search all over again. The 7.0 UI was much better.

I would like to see a proper way to avoid killing the sourcing systems. There is some parameterization in this case if you push down the query to some systems, but I think there are still issues with giving this tool to end users because they could write queries that could cause a lot of issues in the operation systems.

We would like this solution to be more universally user-friendly. At present it is really only aimed at IT specialists.

Denodo can improve usage management-related aspects. If you deal with the mini views, it gets stuck. The performance is very slow when we go with a large number of views and high volume. In a future release of Denodo, they could add more features, such as remote tables and metadata for views.

There have been some issues when you are at a table. Currently, Denodo exports data sets for a tabular model. When you are finished modeling your database or data warehouse they export a link to be used in Tableau. They should support other tools like Power BI.

Denodo's training documentation could be improved by providing more material. From an administrative standpoint, I've found that only Denodo websites provide the usual tutorials. It may be because it's a bit of a restricted tool, but it results in trouble with learning. Normally, I can find help and solutions from other sources, but I haven't been able to find any for Denodo. Other that, it's fine and it performs well. I only have six months of experience, so I can't accurately suggest improvements.

I'd like to see integrations with AWS, GCP and the like.

The support is not the best and should be improved. In the future, I would like to see a different structure for how they manage the data sources and connectors. Having a better data lineage tool would also be an improvement. Better audit capabilities would be a useful enhancement.

The dropdown menus feel antiquated to me, and the administrative portals need improvement. In the next release, I would like to see a better user experience and the interface needs modernization.

In our country, we do have to get the training and do the end-to-end delivery, and that can be a bit hectic when it comes to customer systems development. We need a bit more external support from the company. Support has been a real issue for us. We occasionally have some integration issues that we need to work through. In terms of features, et cetera, I don't know if there is anything really missing from that perspective. We are also new to this product. We have to analyze it and other products and that process often takes some time. It's not fair to comment on what's missing without surveying the entire landscape.

Documentation needs to be improved, they need to lift their game. Finding information is difficult. I'm doing the training and they provide courses but it could be improved. I haven't tested the solution for long enough to be able to suggest any additional features.

The integration could use improvement, it's a lot of non-speed line processes that we have discovered, in the country. The configurations could use a lot more improvement.

The solution should have its own acceleration technology. The connectivity is not so great. It uses standard protocols to connect to the data center, it could improve the interface in terms of automation. The connection should be easier for the end-user. At the moment it's a bit too complex. You need a lot of documentation.

The data catalog certainly has room for improvement. It is functional but we look forward to development. We are in constant contact with Denodo and they are fully aware of our needs. I'd like to see an improvement to data catalog functionality which would immensely increase the value of this product. In our organization, when we have to analyze a lot of data, the possibility to represent the very meaning of data to the analysts, which is actually the functionality of data catalog, is very important. Denodo is very good at creating unified access to data. It's not that good yet, in the integration of the semantics of the data, in determining what the data means. In a statistics organization, the integration with a metadata system is extremely important. That's the reason why we have found a way to integrate our metadata system with Denodo data catalog. It's easy to imagine much more functionality and we know that Denodo is fully aware of that. Denodo is improving its data catalog functionality as a result. It's not to say that we are not satisfied with the existing one but we'd like to see improvements.