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.
"It is an ETL tool, which does the extract, transform, and load."
"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 like that Oracle Data Integrator (ODI) has a straightforward setup and offers good technical support."
"ODI is a very accessible tool, especially since the mapping functionality has been added."
"Oracle provides great documentation."
"All our systems can be widely integrated by ODI, such as transactional systems, our data warehouses, and B2B integration."
"ODI's best features are customization, integration with other versioning tools, and the ability to define new knowledge modules."
"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 product's deployment phase is easy."
"SSIS' most valuable feature is its reporting services."
"In SSIS, the scope is not only to handle ETL challenges, but it will allow us to do so many other tasks, such as DBA activities, scripting, calling any .exe or scripts, etc."
"It's saved time using visualization descriptions."
"It is easily scheduled and integrates well with SQL Server and SQL Server Agent jobs."
"It has good data integration and good processes."
"It is easy to set up the solution."
"The most important features are it works well and provides self-service BI."
"The initial setup is a bit complex compared to other tools."
"It would be really good if Oracle considered enabling the tool to integrate with some other platforms that are deprecated simply for commercial reasons"
"Technical Support could be better."
"We used a third party to do the implementation of ODI."
"The performance of the user interface is in need of improvement."
"The initial setup is complex, especially if you also have to install a console."
"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."
"There are certain things where it can be improved. Initial solution setup seems a bit complex at the start, it should be improved because it becomes bit tough for a novice to get started on this. Sometimes error description is not helpful to understand the problem it gives some generic type of errors which are at times not that helpful to understand the underlying root cause of the issue."
"It's a legacy tool, that is nearing the end of its useful life."
"It's difficult to refactor SSIS. It gets cumbersome to reuse the solution."
"The security could be improved, as it is more important in our context."
"I would like to see better integration with Power BI."
"Sometimes when we want to publish to other types of databases it's not easy to publish to those databases. For example, the Jet Database Engine. Before the SSIS supported Jet Database Engine but nowadays it doesn't support the Jet Database Engine. We connect to many databases such as Access database, SparkPros databases and the other types of databases using Jet Database Engines now and SSIS now doesn't seem to support it in our databases."
"SSIS should be made a little bit more intuitive and user-friendly because it needs an expert-level person to work on it."
"Sometimes we need to connect to AWS to get additional data sources, so we have to install some external LAN and not a regular RDBMS. We need external tools to connect. It would be great if SSIS included these tools. I'd also like some additional features for row indexing and data conversion."
"I would like to see better technical documentation because many times information is missing."
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?