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 Knowledge Module approach provides an easy and reusable way to create our own integration strategies. It's easy to create these Knowledge Modules to connect to new technologies, for instance."
"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."
"The scalability is great. It's one of the reasons we chose the solution."
"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."
"It has the ability to easily load slowly changing dimensions."
"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."
"Besides loading data, we do most of our transformations in ODI."
"In our DW/BI solution, ODI is the main tool to integrate the data in a daily batch way."
"Like most Microsoft products, SSIS is user-friendly and easy to use."
"This solution is easy to implement, has a wide variety of connectors, has support for Visual Basic, and supports the C language."
"The script component is very powerful, things that you cannot normally do, is feasible through C#."
"SSIS' best feature is SFTP connectivity."
"The interface is very user-friendly."
"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 product's deployment phase is easy."
"SSIS' most valuable feature is its reporting services."
"The performance of the user interface is in need of improvement."
"It needs easier security."
"Technical Support could be better."
"The initial setup is a bit complex compared to other tools."
"The resource management aspect of the solution could be improved."
"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."
"It would be really good if Oracle considered enabling the tool to integrate with some other platforms that are deprecated simply for commercial reasons"
"The solution lacks some functions and features."
"We have a stability problem because when something works, it works one time. The next time, it doesn't work."
"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 would like to see better technical documentation because many times information is missing."
"Improving the login procedure would make our reporting easier on monitoring our ETL processes."
"The debugging could be improved because when it came to solving the errors that I've experienced in the past, I've had to look at the documentation for more information."
"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."
"There are a lot of things that Microsoft could improve in relation to SSIS. One major problem we faced was when attempting to move some Excel files to our SQL Server. The Excel provider has a limitation that prevents importing more than 255 columns from a particular Excel file to the database. This restriction posed a significant issue for us."
Oracle Data Integrator (ODI) is ranked 4th in Data Integration with 65 reviews while SSIS is ranked 2nd in Data Integration with 68 reviews. Oracle Data Integrator (ODI) is rated 8.2, while SSIS is rated 7.8. 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 : https://www.hitachivantara.com/en-us/pdf/brochure/leverage-open-source-benefits-with-assurance-of-hitachi-overview.pdf
And a short description of the community edition: https://www.predictiveanalyticstoday.com/pentaho-community-edition/
And the download link: https://community.hitachivantara.com/s/article/downloads
You can ask more from the great community: https://forums.pentaho.com/
Regards
Károly
We usually use Talend.
Look here: https://community.talend.com/t5/Design-and-Development/The-way-from-OLTP-to-OLAP/td-p/116719
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: https://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?