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 installation of the client ODI Studio is easy."
"The solution's initial setup is straightforward, especially compared to Mule, which our team has worked with before and found to be a bit more complex in terms of setup."
"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."
"Oracle provides great documentation."
"It can integrate with more recent databases like Cassandra, Hadoop, and other more recent Big Data databases."
"What I found most valuable in Oracle Data Integrator (ODI) is that it integrates well with almost all technologies currently being used in my company."
"Besides loading data, we do most of our transformations in ODI."
"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 solution is stable."
"It's already very user-friendly and has a good dashboard."
"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."
"Its compatibility with Microsoft products has been very valuable to our company. It fits well within the architecture."
"The performance is good."
"It is easily scheduled and integrates well with SQL Server and SQL Server Agent jobs."
"Built in reports show package execution and messages. Logging can also be customized so only what is needed is logged. There is also an excellent logging replacement called BiXpress that provides both historical and real-time monitoring which is more efficient and much more robust than the built-in logging capabilities. And none of this requires custom coding to make it useful unlike many other ETL tools."
"The initial setup of this solution is very straightforward."
"Important features include that it comprises lots of functionality to connect data from various sources through connector availability, scheduling pipelines at any time, and integration with third-party and security solutions for encryption."
"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."
"The most valuable feature is the pipelines because they enable us to pull in and push out data from different sources and to manipulate and clean things up within them."
"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"
"The best thing about StreamSets is its plugins, which are very useful and work well with almost every data source. It's also easy to use, especially if you're comfortable with SQL. You can customize it to do what you need. Many other tools have started to use features similar to those introduced by StreamSets, like automated workflows that are easy to set up."
"StreamSets’ data drift resilience has reduced the time it takes us to fix data drift breakages. For example, in our previous Hadoop scenario, when we were creating the Sqoop-based processes to move data from source to destinations, we were getting the job done. That took approximately an hour to an hour and a half when we did it with Hadoop. However, with the StreamSets, since it works on a data collector-based mechanism, it completes the same process in 15 minutes of time. Therefore, it has saved us around 45 minutes per data pipeline or table that we migrate. Thus, it reduced the data transfer, including the drift part, by 45 minutes."
"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 most valuable would be the GUI platform that I saw. I first saw it at a special session that StreamSets provided towards the end of the summer. I saw the way you set it up and how you have different processes going on with your data. The design experience seemed to be pretty straightforward to me in terms of how you drag and drop these nodes and connect them with arrows."
"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 performance of the user interface is in need of improvement."
"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."
"The initial setup is complex, especially if you also have to install a console."
"The tool should improve its pricing. It prevents the application of Oracle ODI on small and medium projects in countries like Croatia, Germany, or the US. While there are no technological obstacles to using it, the high price makes it unfeasible for projects with smaller budgets."
"ODI could improve the ease of use. There is a steep learning curve to use the solution."
"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."
"The price needs to be lowered. It's too expensive."
"We purchase an add on called task factory primarily to allow bulk delete, update and upsert capability. I'd like to see this be part of the standard package."
"I have a tool called ZappySys. I need that tool to cut down on the complexity of SSIS. That tool really helps with a quick turnaround. I can do things quickly, and I can do things accurately. I can get better reporting on errors."
"At one point, we did have to purchase an add-on."
"Microsoft's technical support has decreased in quality over the last few years, becoming less responsive and tending to pass problems on instead of solving them."
"SSIS is stable, but extensive ETL data processing can have some performance issues."
"Sometimes when we want to publish to other types of databases it's not easy to publish to those databases. For example, the Jet Database Engine. Before the SSIS supported Jet Database Engine but nowadays it doesn't support the Jet Database Engine. We connect to many databases such as Access database, SparkPros databases and the other types of databases using Jet Database Engines now and SSIS now doesn't seem to support it in our databases."
"The solution should work on the GPU, graphical processing unit. There should also be piping integration available."
"The performance of SSIS could improve when comparing it to Oracle Database."
"Using ETL pipelines is a bit complicated and requires some technical aid."
"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."
"We often faced problems, especially with SAP ERP. We struggled because many columns weren't integers or primary keys, which StreamSets couldn't handle. We had to restructure our data tables, which was painful. Also, pipeline failures were common, and data drifting wasn't addressed, which made things worse. Licensing was another issue we encountered."
"The documentation is inadequate and has room for improvement because the technical support does not regularly update their documentation or the knowledge base."
"StreamSet works great for batch processing but we are looking for something that is more real-time. We need latency in numbers below milliseconds."
"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."
"I would like to see further improvement in the UI. In addition, upgrades are not automatic and they should be automated. Currently, we have to manually upgrade versions."
"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."