Oracle Data Integrator is an ELT data integrator designed with interoperability other Oracle programs. The program focuses on a high-performance capacity to support Big Data use within Oracle.
N/A
Oracle Warehouse Builder
Score 8.7 out of 10
N/A
Oracle Warehouse Builder (OWB) is a data-warehousing centered data integration solution, from Oracle. It offers basic ETL functionality for building a simple data warehouse, as well as advanced ETL functionality supporting enterprise data integration projects, along with connectivity for Oracle and SAP applications.
N/A
Progress MarkLogic
Score 9.0 out of 10
N/A
MarkLogic Server is a multi-model database that has both NoSQL and trusted enterprise data management capabilities. The vendor states it is the most secure multi-model database, and it’s deployable in any environment. They state it is an ideal database to power a data hub.
$0.01
per MCU/per hour + 0.10 per GB/per month
Pricing
Oracle Data Integrator (ODI)
Oracle Warehouse Builder
Progress MarkLogic
Editions & Modules
No answers on this topic
No answers on this topic
Low Priority Fixed
$0.01
per MCU/per hour + 0.10 per GB/per month
Standard Reserved
$0.07
per MCU/per hour + 0.10 per GB/per month
Standard On-Demand
$0.13
per MCU/per hour + 0.10 per GB/per month
Offerings
Pricing Offerings
Oracle Data Integrator (ODI)
Oracle Warehouse Builder
Progress MarkLogic
Free Trial
No
No
No
Free/Freemium Version
No
No
No
Premium Consulting/Integration Services
No
No
No
Entry-level Setup Fee
No setup fee
No setup fee
No setup fee
Additional Details
—
—
—
More Pricing Information
Community Pulse
Oracle Data Integrator (ODI)
Oracle Warehouse Builder
Progress MarkLogic
Considered Multiple Products
Oracle Data Integrator (ODI)
Verified User
Consultant
Chose Oracle Data Integrator (ODI)
Oracle's own ETL tool was Oracle Warehouse Builder, initially. When Oracle built the Oracle Business Intelligence Applications Suite, Oracle is in need of a strong ETL. As Oracle Warehouse Builder is not a strong ETL that customers prefer and as already Informatica captured …
ODI is the naturel successor of OWB, adopting the same EL-T approach but supporting a lot more technologies as source and target. The overall product is much more stable and not tied to the Oracle Database. Unlike Informatica, ODI generates all the code in the native underlying …
Depending on investment, I would prefer Oracle Data Integrator, since it complies with all versions of all types of databases including Big Data, Hadoop and NoSQL environment as well as the cloud and is the strategic heterogenous data integration product of Oracle, as it is …
I think that Oracle Warehouse Builder is easier to use the Oracle Data Integrator (ODI). The connections in Oracle Warehouse Builder (OWB) are easier to understand when troubleshooting. Anything that makes troubleshooting easier gets higher marks in my book. ODI wins in the …
Oracle Data Integrator is well suited in all the situations where you need to integrate data from and to different systems/technologies/environments or to schedule some tasks. I've used it on Oracle Database (Data Warehouses or Data Marts), with great loading and transforming performances to accomplish any kind of relational task. This is true for all Oracle applications (like Hyperion Planning, Hyperion Essbase, Hyperion Financial Management, and so on). I've also used it to manage files on different operating systems, to execute procedures in various languages and to read and write data from and to non-Oracle technologies, and I can confirm that its performances have always been very good. It can become less appropriate depending on the expenses that can be afforded by the customer since its license costs are quite high.
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.
If you are storing META data then MarkLogic is super useful as it retrieves everything so fast, while storing the whole data shows performance issues some times. If you have legacy systems then migrating from it would really require sweat and blood, on the other hand if you are in systems like Node.js you can simply integrate two systems easily. If you don't know how in the end your your data schema will look like then it's better to make a prototype using MarkLogic.
Oracle Data Integrator nearly addresses every data issue that one can expect. Oracle Data Integrator is tightly integrated to the Oracle Suite of products. This is one of the major strengths of Oracle Data Integrator. Oracle Data Integrator is part of the Oracle Business Intelligence Applications Suite - which is highly used by various industries. This tool replaced Informatica ETL in Oracle Business Intelligence Applications Suite.
Oracle Data Integrator comes with many pre-written data packages. If one has to load data from Excel to Oracle Database, there is a package that is ready available for them - cutting down lot of effort on writing the code. Similarly, there are packages for Oracle to SQL, SQL to Oracle and all other possible combinations. Developers love this feature.
Oracle Data Integrator relies highly on the database for processing. This is actually an ELT tool rather than an ETL tool. It first loads all the data into target instance and then transforms it at the expense of database resources. This light footprint makes this tool very special.
The other major advantage of Oracle Data Integrator, like any other Oracle products, is a readily available developer pool. As all Oracle products are free to download for demo environments, many organizations prefer to play around with a product before purchasing it. Also, Oracle support and community is a big advantage compared to other vendors.
ODI does not have an intuitive user interface. It is powerful, but difficult to figure out at first. There is a significant learning curve between usability, proficiency, and mastery of the tool.
ODI contains some frustrating bugs. It is Java based and has some caching issues, often requiring you to restart the program before you see your code changes stick.
ODI does not have a strong versioning process. It is not intuitive to keep an up to date repository of versioned code packages. This can create versioning issues between environments if you do not have a strong external code versioning process.
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.
MarkLogic still has a long way to go in fostering the developer community. Many developers are gravitating to the simple integrations and do not delve into the deeper capabilities. They have made tremendous strides in recent months and I am sure this will improve over time.
Many of the best features are left on the floor by enterprises who end up implementing MarkLogic as a data store. MarkLogic needs to help customers find ways to better leverage their investment and be more creative in how they use the product.
Licensing costs become a major hurdle for adoption. The pricing model has improved for basic implementations, but the costs seem very prohibitive for some verticals and for some of the most advanced features.
It is maturing and over time will have a good pool of resources. Each new version has addressed the issues of the previous ones. Its getting better and bigger.
MarkLogic is expensive but solid. While we use open source for almost everything else, the backend database is too critically important. At this point, re-tooling for a different back end would take too much time to be a viable option.
Oracle Data Integrator (ODI) is a reliable ELT tool, supporting data loads from various heterogenous sources. It is effective both for structured as well as non structured data. Its works well for creating translations and transformation and also aids in the data quality checks when combined with an MDM solution. Troubleshooting issues can be of a challenge if it is not configured properly.
Very little about it can be done better or with greater ease. Even things that seem difficult aren't really that bad. There's multiple ways to accomplish any admin task. MarkLogic requires a fraction of administrative effort that you see with enterprise RDBMS like Oracle. MarkLogic is continually improving the tools to simplify cluster configuration and maintenance.
There's always room for improvement. Some problems get solved faster than others, of course. MarkLogic's direct support is very responsive and professional. If they can't help immediately, they always have good feedback and are eager to receive information and details to work to replicate the problem. They are quick to escalate major support issues and production show-stopping problems. In addition to MarkLogic's direct support, there are several employees who are very active among the community and many questions and common issues get quick attention from helpful responses to email and StackOverflow questions.
I have used Trifacta Google Data Prep quite a bit. We use Google Cloud Platform across our organization. The tools are very comparable in what they offer. I would say Data Prep has a slight edge in usability and a cleaner UI, but both of the tools have comparable toolsets.
We had Fast in place when Microsoft had bought it up and was going to change / deprecate it. One of the biggest advantages of MarkLogic for search actually had to do with the rest of the content pipeline - it allowed us to have it all in one technology. On the NoSQL side, we looked at MongoDB a couple years back. At that time, MarkLogic came in stronger on indexing, transaction reliability, and DR options. For us, that was worth using a commercial product.
MarkLogic reduced the amount of time that the DevOps team needed to dedicate to database updates, as the engineering team was mostly able to easily design and maintain database upgrades without requiring specialists such as database architects on the DevOps side. This capability flowed from the product's speed and the versatility of its XQuery language and libraries.
MarkLogic required significant education and buy-in time for the engineering team.
