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.
"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 scalability is great. It's one of the reasons we chose the solution."
"The installation of the client ODI Studio is easy."
"The product has an ELT approach."
"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 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."
"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."
"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 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."
"I have found its most valuable features to be its package management capabilities and the flexibility it offers in designing workflows."
"The performance and stability are good."
"The script component is very powerful, things that you cannot normally do, is feasible through C#."
"The main value of any Microsoft product is the ease of use. You can achieve more with less time. That's what's beneficial for me. With many competitors, you might need to spend more time coming up with a solution because you have to focus on taking care of the product."
"It is also easy to learn and user-friendly. Microsoft is also good in terms of technical support. They have built a large community all over the world."
"It's a competent product."
"The most valuable thing is that it is easy to connect with Microsoft tools. In Europe, particularly in France, a lot of companies use Excel, SQL Server, and other Microsoft tools, and it is easier to connect SSIS with Microsoft tools than other products."
"Overall the product is fine, but sometimes its reports unknown errors while we compile ETL scripts."
"The resource management aspect of the solution could be improved."
"If there was an add-on tool to hide the performance issues and solve them for me, then I might be interested in that as it would provide me value."
"The price needs to be lowered. It's too expensive."
"I would only point out some minor bugs or glitches in the development interface (ODI studio)."
"Reverse engineering is complicated and challenging to manage."
"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."
"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."
"Options for scaling could be improved."
"We In upgrading SSIS, we encountered challenges fixing SQL Server and performance issues, including problems during a failover in our data warehouse."
"The solution could improve by having quicker release updates."
"Video training would be a helpful addition."
"The performance of this solution is not as good as other tools in the market."
"SSIS is stable, but extensive ETL data processing can have some performance issues."
"I would like to see more standard components out of the box, such as SFTP, and Data Compression components."
"We'd like them to develop data exploration more."
Oracle Data Integrator (ODI) is ranked 4th in Data Integration with 15 reviews while SSIS is ranked 2nd in Data Integration with 33 reviews. Oracle Data Integrator (ODI) is rated 8.2, while SSIS is rated 7.6. The top reviewer of Oracle Data Integrator (ODI) writes "We can make all the EPM tools work together as one and we can create a puzzle that will increase the performance and capability of all EPM tools". On the other hand, the top reviewer of SSIS writes "SSIS 2016 - The good, the bad, and the ugly". 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?