Denodo vs. Oracle Warehouse Builder

Denodo allows us to create and combine new views to create a
virtual repository and APIs without a single line of code. It is excellent
because it can present connectors with a view format for downstream consumers
by flattening a JSON file. Reading or connecting to various sources and
displaying a tabular view is an excellent feature. The product's technical data
catalog is well-organized.

Incentivized

The best place for Oracle Warehouse Builder is at the business IT level. It's not suited for business-level users. They are easy confused. One way to reduce the confusion for the developers is to set up the workspaces based on the requirements that are discovered in design sessions. Once this is complete, the implementation of Oracle Warehouse Builder can take flight and be successful.

Incentivized

• Database Agnostic: You can easily connect to different environments and mash up data sets.
• The "magic" of data virtualization: No data is created, so data is reported in near-real-time to end users.
• It's easy to use UI for developers. You just connect to a data source, create tables, and join them to other datasets.

Incentivized

• Easy transformation.
• Easy implementation from Oracle to Oracle systems.
• Ease of usage and easy to learn.
• Starting component of metadata management.

Incentivized

• Caching - but I am sure it will be improved by now. There were times when we expected the cache to be refreshed but it was stale.
• Schema generation of endpoints from API response was sometimes incomplete as not all API calls returned all the fields. Will be good to have an ability to load the schema itself (XSD/JSON/Soap XML etc).
• Denodo exposed web services were in preliminary stage when we used; I'm sure it will be improved by now.
• Export/Import deployment, while it was helpful, there were unexpected issues without any errors during deployment. Issues were only identified during testing. Some views were not created properly and did not work. If it was working in the environment from where it was exported from, it should work in the environment where it is imported.

Incentivized

• What I noticed is that sometimes OWB doesn't generate the best SQL in the package especially when there are a high number of source tables in the ETL. It would be nice if ETL developers were allowed to update the generated packages in the database directly.
• Another thing - moving OWB ETLs from one database to another one could be easier - for example it would be nice to just copy the generated packages from one database to the other one without doing the deployment of these ETLs through OWB.

Incentivized

Denodo is very easy to use. It has a user-friendly drag and drop interface. I'm not a fan of the java platform it resides on.

Incentivized

Denodo is a tool to rapidly mash data sources together and create meaningful datasets. It does have its downfalls though. When you create larger, more complex datasets, you will most likely need to cache your datasets, regardless of how proper your joins are set up. Since DV takes data from multiple environments, you are taxing the corporate network, so you need to be conscious of how much data you are sending through the network and truly understand how and when to join datasets due to this.

Incentivized

Denodo is simple and easy to use. Highly recommended unless you have huge volumes of data

Incentivized

Ab>initio, IBM Datastage 8.0

Incentivized

• It is a huge advantage that we can connect to many different databases to provide data rapidly and accurately.
• It has proven to be a valuable environment for deploying data virtualization solutions, and its user community is active in finding and fixing issues.

Incentivized

• It improved understanding of ETL functions. Data is consistent. The speed is pretty good.

Incentivized