We performed a comparison between Oracle Data Integrator (ODI), SSIS, and StreamSets based on real PeerSpot user reviews.
Find out what your peers are saying about Microsoft, Informatica, Oracle and others in Data Integration."The CAEM is very useful in its modularity and portability."
"The product has an ELT approach."
"The most valuable feature that we use is the Knowledge Modules."
"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."
"Besides loading data, we do most of our transformations in ODI."
"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 tool improved our data integration workflow primarily due to its compatibility with Oracle. Its integration makes it very convenient for analytics. Its most valuable feature is robust extended capability. The solution's debugging capabilities are good."
"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 setup was easy. All Microsoft products are easy to set up."
"The simplicity of the solution is great. The solution also offers excellent integration."
"SSIS' most valuable feature is its reporting services."
"It's already very user-friendly and has a good dashboard."
"The script component is very powerful, things that you cannot normally do, is feasible through C#."
"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 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 has good data integration and good processes."
"The most valuable features are the option of integration with a variety of protocols, languages, and origins."
"The ability to have a good bifurcation rate and fewer mistakes is valuable."
"The best feature that I really like is the integration."
"It is really easy to set up and the interface is easy to use."
"The UI is user-friendly, it doesn't require any technical know-how and we can navigate to social media or use it more easily."
"In StreamSets, everything is in one place."
"It is a very powerful, modern data analytics solution, in which you can integrate a large volume of data from different sources. It integrates all of the data and you can design, create, and monitor pipelines according to your requirements. It is an all-in-one day data ops solution."
"It's very easy to integrate. It integrates with Snowflake, AWS, Google Cloud, and Azure. It's very helpful for DevOps, DataOps, and data engineering because it provides a comprehensive solution, and it's not complicated."
"The resource management aspect of the solution could be improved."
"Overall the product is fine, but sometimes its reports unknown errors while we compile ETL scripts."
"It would be really good if Oracle considered enabling the tool to integrate with some other platforms that are deprecated simply for commercial reasons"
"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 solution lacks some functions and features."
"The stability of the software could be improved. Sometimes, the software just crashes. "
"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."
"An area for improvement would be the lack of SQL compatibility - ODI has no ability to interact with SQL unstructured types and data types."
"When I compare Talend and SSIS, Talend provides more features. With Talend, we can handle a large volume of data. Talend is usually used to treat a large volume of data, which makes it better than SSIS on the data side. Talend also has a very good Talend Management Console to schedule the jobs and do other things. It can also be easily connected to version control tools such as GitHub or SVN. The last time I used SSIS, it was connected through TSS for the Windows Console version. I am not sure it has been improved or not. If it is not improved, Microsoft should improve it. They should change the product to provide another console."
"Options for scaling could be improved."
"The solution should work on the GPU, graphical processing unit. There should also be piping integration available."
"I would like to see more features in terms of the integration with Azure Data Factory."
"I would like to see more standard components out of the box, such as SFTP, and Data Compression components."
"The creation of the measure in the DAC's model could be improved."
"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."
"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."
"In terms of the product, I don't think there is any room for improvement because it is very good. One small area of improvement that is very much needed is on the knowledge base side. Sometimes, it is not very clear how to set up a certain process or a certain node for a person who's using the platform for the first time."
"They need to improve their customer care services. Sometimes it has taken more than 48 hours to resolve an issue. That should be reduced. They are aware of small or generic issues, but not the more technical or deep issues. For those, they require some time, generally 48 to 72 hours to respond. That should be improved."
"We've seen a couple of cases where it appears to have a memory leak or a similar problem."
"The execution engine could be improved. When I was at their session, they were using some obscure platform to run. There is a controller, which controls what happens on that, but you should be able to easily do this at any of the cloud services, such as Google Cloud. You shouldn't have any issues in terms of how to run it with their online development platform or design platform, basically their execution engine. There are issues with that."
"The software is very good overall. Areas for improvement are the error logging and the version history. I would like to see better, more detailed error logging information."
"I would like to see it integrate with other kinds of platforms, other than Java. We're going to have a lot of applications using .NET and other languages or frameworks. StreamSets is very helpful for the old Java platform but it's hard to integrate with the other platforms and frameworks."
"One thing that I would like to add is the ability to manually enter data. The way the solution currently works is we don't have the option to manually change the data at any point in time. Being able to do that will allow us to do everything that we want to do with our data. Sometimes, we need to manually manipulate the data to make it more accurate in case our prior bifurcation filters are not good. If we have the option to manually enter the data or make the exact iterations on the data set, that would be a good thing."
"Currently, we can only use the query to read data from SAP HANA. What we would like to see, as soon as possible, is the ability to read from multiple tables from SAP HANA. That would be a really good thing that we could use immediately. For example, if you have 100 tables in SQL Server or Oracle, then you could just point it to the schema or the 100 tables and ingestion information. However, you can't do that in SAP HANA since StreamSets currently is lacking in this. They do not have a multi-table feature for SAP HANA. Therefore, a multi-table origin for SAP HANA would be helpful."
