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.
"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."
"ODI's most valuable features are it utilizes the database engine and is very lightweight."
"It can integrate with more recent databases like Cassandra, Hadoop, and other more recent Big Data databases."
"Oracle provides great documentation."
"ODI's best features are customization, integration with other versioning tools, and the ability to define new knowledge modules."
"It's completely user-friendly."
"Most of the functions are very straightforward, like the data model, mapping, package, and load plan. Thus, a new user could get started very fast."
"I do not have to maintain a separate ETL instance. I can change the SQL when something is not performing correctly."
"The performance is good."
"The ability of SSIS to transform and transport data is extremely valuable to me. It allows for intelligent extraction and manipulation of data during the process. Improved error handling would enhance ETL processes further. I haven't directly utilized the data flow components but they seem capable of supporting complex data integration needs."
"The scalability of SSIS is good."
"The setup was easy. All Microsoft products are easy to set up."
"It's a competent product."
"The technical support is very good."
"The most valuable feature of SSIS is that it can handle real complex transformations."
"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 initial setup is complex, especially if you also have to install a console."
"It lacks a suite of tools suitable for fully processing data and moving it into decision support warehouses."
"The tool should improve its pricing. It prevents the application of Oracle ODI on small and medium projects in countries like Croatia, Germany, or the US. While there are no technological obstacles to using it, the high price makes it unfeasible for projects with smaller budgets."
"Oracle Data Integrator (ODI) is already good as a solution. Still, it needs some editing of its preview package, or if the package is upgraded, that will make Oracle Data Integrator (ODI) even better."
"An area for improvement would be the lack of SQL compatibility - ODI has no ability to interact with SQL unstructured types and data types."
"It has been very good. Just recently, I've faced an issue, but I solved it somehow. While integrating with a file, I faced an issue where I wanted output files, and I had used the text field limited quotations, but at the end of the file, there was a line breakage for the last column. So, we just removed the text field because it was not working correctly for us."
"The performance of the user interface is in need of improvement."
"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 high prices attached to the product can be an area of concern where improvements are required."
"Future releases should improve the data lineage, as it currently is not good."
"SSIS can improve by the minimum code requirements in stored procedures and exporting data is difficult. They could make it easier, it should be as easy as it is to import data."
"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."
"SSIS sometimes hangs, and there are some problems with servers going down after they've been patched."
"Options for scaling could be improved."
"There was also not enough instructions from Microsoft in regards to this application or this technology, which can easily be improved upon."
"It hangs a lot of the time."
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?