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 feature of ODI is the to use of the whole ETL to create a data lake."
"Besides loading data, we do most of our transformations in ODI."
"ODI's best features are customization, integration with other versioning tools, and the ability to define new knowledge modules."
"All ETL code is stored in repositories in underlying database schemas. The number of users can access and work on the same solution using a client tool. So distributed teams can work on this tool in an efficient manner."
"The solution's initial setup is straightforward, especially compared to Mule, which our team has worked with before and found to be a bit more complex in terms of setup."
"It's scalable."
"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."
"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."
"This solution is easy to implement, has a wide variety of connectors, has support for Visual Basic, and supports the C language."
"SSIS' most valuable feature is its reporting services."
"The most important features are it works well and provides self-service BI."
"I have used most of the standard SQL features, but the ones that stand out are the Data Flows and Bulk Import."
"The most valuable feature of SSIS is that you can take data from other servers which are not MS SQL Server or Oracle."
"The most valuables features are the relatively short learning curve, and the automation capabilities provided through the BIML add-in for SSDT."
"The performance and stability are good."
"SSIS is easy to use."
"It would be really good if Oracle considered enabling the tool to integrate with some other platforms that are deprecated simply for commercial reasons"
"I rate it a seven out of 10 because there is room for growth because ODI is still new, in comparison to Informatica, which is a mature product."
"In our company, we haven't tried consuming services from IoT in our company yet, and I would like to know if the solution will support IoT services in the next release."
"It needs easier security."
"At present, when multiple steps are executed in parallel in the load plan and errors occur, the error handling mechanism does not function correctly."
"An area for improvement in Oracle Data Integrator (ODI) is real-time integration. Currently, my company has a workaround to implement real-time integration, an area on which Oracle must focus more. Real-time integration should be easier in Oracle Data Integrator (ODI). Another area for improvement in Oracle Data Integrator (ODI) is integration with more publishers and subscribers rather than just database integrations."
"An area for improvement would be the lack of SQL compatibility - ODI has no ability to interact with SQL unstructured types and data types."
"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."
"Involving a data lake or data engineering aspects would be useful. While it is there, we need more features included."
"Sometimes, there are compatibility issues with some features. From time to time, I also face issues when trying to migrate. If I misconfigure things when I use Snapshot, the migration will fail.It can take a long time to migrate huge amounts of data, so it would be nice if that could be faster."
"SSIS is stable, but extensive ETL data processing can have some performance issues."
"The solution could improve by having quicker release updates."
"We're in the process of switching to Informatica, and we need to work out data lineage and data profiling and to improve the quality of our data. SSIS, however, is not that compatible with Informatica. We managed to connect it to Informatica Metadata Manager, but we don't get good lineage, so we have to redo all our ETLs using the Informatica process in order to accept the proper data lineage."
"Microsoft's technical support has decreased in quality over the last few years, becoming less responsive and tending to pass problems on instead of solving them."
"I would like to see more features in terms of the integration with Azure Data Factory."
"We purchase an add on called task factory primarily to allow bulk delete, update and upsert capability. I'd like to see this be part of the standard package."
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?