We performed a comparison between Oracle Data Integrator (ODI) and SSIS based on our users’ reviews in five categories. After reading all of the collected data, you can find our conclusion below.
Comparison Results: Users seem to be more satisfied with SSIS because of its ease of deployment, its features, and its pricing.
"The most valuable features of ODI are the ease of development, you can have a template, and you can onboard transfer very quickly. There's a lot of knowledge modules available that we can use. If you want to connect, for example, a Sibyl, SQL, Oracle, or different products, we don't have to develop them from scratch. They are available, but if it's not, we can go into the marketplace and see if there's a connector there. Having the connector available reduces the amount of hard work needed. We only have to put the inputs and outputs. In some of the products, we use there is already integration available for ODI, which is helpful."
"One of the standout features of ODI is its ability to prepare everything on a vertical level and create reusable components, which adds to its value."
"The initial setup is easy."
"What I found most valuable in Oracle Data Integrator (ODI) is that it integrates well with almost all technologies currently being used in my company."
"It can integrate with more recent databases like Cassandra, Hadoop, and other more recent Big Data databases."
"The most valuable features of ODI are the knowledge modules, such as the Loading Knowledge module and the Check Knowledge module, they are helpful. We can check for the constraints in ODI. That helps in figuring out what are the constraints that are the primary keys created in the tables. We can check them with the Check Knowledge module."
"The tool improved our data integration workflow primarily due to its compatibility with Oracle. Its integration makes it very convenient for analytics. Its most valuable feature is robust extended capability. The solution's debugging capabilities are good."
"It allows us to use many languages to develop and to integrate practically all the technologies of the Oracle suite as well as those from non-Oracle vendors."
"Data Flows are the main component we use. These can range from a simple source to sink ETL, to many source to many sink dataflows."
"It has the ability to be deployed into the cloud through Data Factory, and run completely as a software as a service in the cloud."
"The workflow features have been very valuable. You can have automated workflows and all the steps are controlled. The workflow functionality of integration services is excellent."
"The reporting on the solution is perfect. I didn't expect to see reporting features, but they are great."
"There are many good features in this solution including the data fields, database integration, support for SQL views, and the lookups for matching information."
"The debugging capabilities are great, particularly during data flow execution. You can look into the data and see what's going on in the pipeline."
"It is easily scheduled and integrates well with SQL Server and SQL Server Agent jobs."
"We can connect with multiple data sources easily using an external connector in SSIS."
"ODI could improve the ease of use. There is a steep learning curve to use the solution."
"The interface of ODI could be improved. For example, navigating and finding functions can be difficult. For example, you have to know which step you need to go to look at where your job status is. The logical step is a bit complex compared to other tools. It's much easier to get a graphical view, but with ODI, it's graphical, plus you have to know all the other pieces that fit around it. You have to think about the logical and physical aspects."
"It needs easier security."
"We used a third party to do the implementation of ODI."
"At present, when multiple steps are executed in parallel in the load plan and errors occur, the error handling mechanism does not function correctly."
"The initial setup is a bit complex compared to other tools."
"Overall the product is fine, but sometimes its reports unknown errors while we compile ETL scripts."
"The solution lacks some functions and features."
"SSIS doesn't have a very good user interface, but if you can work with it, it'll provide you with almost all of the functionality."
"SSIS is stable, but extensive ETL data processing can have some performance issues."
"Generic processes should be used instead of custom code for each table."
"I come from a coding background and this tool is graphically based. Sometimes I think it's cumbersome to do mapping graphically. If there was a way to provide a simple script, it would be helpful and make it easier to use."
"In terms of its performance, it could be better. That could be something that would be easy and welcomed as an upgrade."
"We would like the solution to be expanded so that it is available for other platforms than just Microsoft."
"A change in the metadata source cripples the whole ETL process, requiring each module to be manually reopened."
"It should have other programming languages supported as well from a scripting perspective. Currently, only C# and VB.NET are supported, which limits it to .NET. It should have Java support as well."
Oracle Data Integrator (ODI) is ranked 4th in Data Integration with 67 reviews while SSIS is ranked 2nd in Data Integration with 69 reviews. Oracle Data Integrator (ODI) is rated 8.2, while SSIS is rated 7.6. The top reviewer of Oracle Data Integrator (ODI) writes "Straightforward to implement, scalable, and has good stability and documentation, but technical support could still be improved". On the other hand, the top reviewer of SSIS writes "Maintaining the solution and contacting its support team is easy". Oracle Data Integrator (ODI) is most compared with Oracle Integration Cloud Service, Informatica PowerCenter, Azure Data Factory, Oracle GoldenGate and Talend Open Studio, whereas SSIS is most compared with Informatica PowerCenter, Talend Open Studio, IBM InfoSphere DataStage, AWS Glue and Azure Data Factory. See our Oracle Data Integrator (ODI) vs. SSIS report.
See our list of best Data Integration vendors.
We monitor all Data Integration reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.
There are two products I know about
* TimeXtender : Microsoft based, Transformation logic is quiet good and can easily be extended with T-SQL , Has a semantic layer that generates metat data for cubes . price approx 40K$, works with tables
. Attunity (Bought by Qlik) : technology agnostic , nice web interface , expensive > 100K€. Works with transaction logs
There are many other pure ETL tools
* ERWIN has a nice one ,
Depends upon the technologies being used. If you're using Oracle for both OLTP and OLAP then you'll get a lot of value from an Oracle solution.
The other question is how up to date do you want your OLAP DB to be? Goldengate is a good answer if you're looking to minimize latency, but it can be expensive. ODI is less expensive but better suited to bulkier data sets. If an Oracle product wasn't the option I'd probably consider something like Informatica.
Hi Rajneesh,
yes here is the feature comparison between the community and enterprise edition : www.hitachivantara.com
And a short description of the community edition: www.predictiveanalyticstoday.com
And the download link: community.hitachivantara.com
You can ask more from the great community: forums.pentaho.com
Regards
Károly
We usually use Talend.
Look here: community.talend.com
As someone mentioned, if you're purely Oracle shop and staying that way then there's value with prioritizing Oracle tools. However, let me contrast that with this caveat...
Consider expectations for tool and vendor longevity. Oracle has a long history of retiring and/or replacing tools leaving customers in the cold with prior versions/tools (I've been burned multiple times by Oracle product retirements or replacements including OWB, Oracle Designer2k, Oracle Express, Oracle OEDW, their purchase of Sagent ETL which as later abandoned).
But I would also consider these questions and relative prioritization:
What is your organization's plans for moving to other database technologies?
Where is your org going with on-prem versus cloud solutions? How important are PaaS versus IaaS solutions?
Where is your current staff's expertise?
Prioritize mature over immature tools.
How many sources do you have? What are their technologies and does the integration tool support them?
Is it just moving data from a single ERP such as Oracle EBS to Olap? When you say Olap what do you mean by that? Are you talking Oracle Olap product or something else? That makes a really big difference of course - if your ETL tool doesn't support your source(s) and target(s) then it shouldn't be considered.
Given the industry's trajectory, I myself would highly prioritize PaaS solutions over others.
What is the OLAP that you are using? Hosted in Cloud or on-premise?
The target DB should have its tool to extract data.
Pentaho is a really nice tool if opensource is the only option.
Please think about issues such as upgrade and disaster in the future. These operations are very easy in Pentaho.
I can only suggest one thing for replication and that is Qlik. (ex-Attunity).
Hi Karoly, Thanks for your input. community: forums.pentaho.com is not allowing new registrations for new users. I guess they accept queries from customers only and not from any one. Do you know any other forum, community, SMEs contacts who can help on queries?