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."It has the ability to easily load slowly changing dimensions."
"In our DW/BI solution, ODI is the main tool to integrate the data in a daily batch way."
"I do not have to maintain a separate ETL instance. I can change the SQL when something is not performing correctly."
"The initial setup is easy."
"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 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."
"I like that Oracle Data Integrator (ODI) has a straightforward setup and offers good technical support."
"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."
"The most important features are it works well and provides self-service BI."
"With this solution, there is the potential to expand, so that you can immediately write code onto the SQL server."
"The most valuable aspect of this solution is that it is simple to use and it offers a flexible custom script task."
"The most valuable feature of SSIS is its ease of use. It is easier to use than other applications."
"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 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 scalability of SSIS is good."
"The initial setup was easy."
"I have used Data Collector, Transformer, and Control Hub products from StreamSets. What I really like about these products is that they're very user-friendly. People who are not from a technological or core development background find it easy to get started and build data pipelines and connect to the databases. They would be comfortable like any technical person within a couple of weeks."
"The ETL capabilities are very useful for us. We extract and transform data from multiple data sources, into a single, consistent data store, and then we put it in our systems. We typically use it to connect our Apache Kafka with data lakes. That process is smooth and saves us a lot of time in our production systems."
"The Ease of configuration for pipes is amazing. It has a lot of connectors. Mainly, we can do everything with the data in the pipe. I really like the graphical interface too"
"For me, the most valuable features in StreamSets have to be the Data Collector and Control Hub, but especially the Data Collector. That feature is very elegant and seamlessly works with numerous source systems."
"StreamSets Transformer is a good feature because it helps you when you are developing applications and when you don't want to write a lot of code. That is the best feature overall."
"In StreamSets, everything is in one place."
"I really appreciate the numerous ready connectors available on both the source and target sides, the support for various media file formats, and the ease of configuring and managing pipelines centrally."
"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."
"ODI could improve by focusing on streamlining its features without unnecessary overhead."
"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."
"If you have something like Cisco on top of it, you will have endless problems."
"Overall the product is fine, but sometimes its reports unknown errors while we compile ETL scripts."
"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."
"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."
"I would only point out some minor bugs or glitches in the development interface (ODI studio)."
"It lacks a suite of tools suitable for fully processing data and moving it into decision support warehouses."
"SSIS sometimes hangs, and there are some problems with servers going down after they've been patched."
"I would also like to see full integration with our BI because then our full load of data will be available in our organization. They should incorporate an ATL process."
"SSIS is stable, but extensive ETL data processing can have some performance issues."
"The solution should work on the GPU, graphical processing unit. There should also be piping integration available."
"Involving a data lake or data engineering aspects would be useful. While it is there, we need more features included."
"At one point, we did have to purchase an add-on."
"There was also not enough instructions from Microsoft in regards to this application or this technology, which can easily be improved upon."
"It needs more integration tools, so you can connect to different sources."
"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."
"The logging mechanism could be improved. If I am working on a pipeline, then create a job out of it and it is running, it will generate constant logs. So, the logging mechanism could be simplified. Now, it is a bit difficult to understand and filter the logs. It takes some time."
"There aren't enough hands-on labs, and debugging is also an issue because it takes a lot of time. Logs are not that clear when you are debugging, and you can only select a single source for a pipeline."
"Visualization and monitoring need to be improved and refined."
"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."
"StreamSets should provide a mechanism to be able to perform data quality assessment when the data is being moved from one source to the target."
"The monitoring visualization is not that user-friendly. It should include other features to visualize things, like how many records were streamed from a source to a destination on a particular date."
"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."
