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 product has an ELT approach."
"It has the ability to easily load slowly changing dimensions."
"Oracle provides great documentation."
"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."
"The most valuable feature of ODI is the to use of the whole ETL to create a data lake."
"ODI's best features are customization, integration with other versioning tools, and the ability to define new knowledge modules."
"All our systems can be widely integrated by ODI, such as transactional systems, our data warehouses, and B2B integration."
"The CAEM is very useful in its modularity and portability."
"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 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 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."
"SSIS' best feature is SFTP connectivity."
"Like most Microsoft products, SSIS is user-friendly and easy to use."
"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 is easy to set up the solution."
"At present, when multiple steps are executed in parallel in the load plan and errors occur, the error handling mechanism does not function correctly."
"ODI could improve the ease of use. There is a steep learning curve to use the solution."
"Overall the product is fine, but sometimes its reports unknown errors while we compile ETL scripts."
"The performance of the user interface is in need of improvement."
"It would be really good if Oracle considered enabling the tool to integrate with some other platforms that are deprecated simply for commercial reasons"
"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."
"I would only point out some minor bugs or glitches in the development interface (ODI studio)."
"Reverse engineering is complicated and challenging to manage."
"I come from a coding background and this tool is graphically based. Sometimes I think it's cumbersome to do mapping graphically. If there was a way to provide a simple script, it would be helpful and make it easier to use."
"You have to write push down join & lookup SQL to the database yourself via stored procedures or use of the SQL Task to get very high performance. That said, this is a common complaint for nearly all ETL tools on the market and those that offer an alternative such as Informatica offer them at a very expensive add-on price."
"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."
"SSIS should be made a little bit more intuitive and user-friendly because it needs an expert-level person to work on it."
"Options for scaling could be improved."
"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."
"Involving a data lake or data engineering aspects would be useful. While it is there, we need more features included."
"Microsoft should offer an on-premises support warranty for those using that deployment. They seem to be withdrawing from on-premises options."
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?