We performed a comparison between SSIS and StreamSets based on real PeerSpot user reviews.
Find out in this report how the two Data Integration solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."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 performance is good."
"We like that this solution includes a developer edition, free of charge, to allow for training."
"SSIS integrates well with SQL servers and Microsoft products."
"You can get data from any data source with SSIS and dump it to any outside source. It is helpful. Getting, extracting, converting, and dumping data doesn't require much effort because we can do everything in the user interface. You drag and drop, then give the required input. It's intuitive."
"SSIS' most valuable feature is its reporting services."
"The simplicity of the solution is great. The solution also offers excellent integration."
"The data reader is the most valuable feature."
"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."
"The scheduling within the data engineering pipeline is very much appreciated, and it has a wide range of connectors for connecting to any data sources like SQL Server, AWS, Azure, etc. We have used it with Kafka, Hadoop, and Azure Data Factory Datasets. Connecting to these systems with StreamSets is very easy."
"Also, the intuitive canvas for designing all the streams in the pipeline, along with the simplicity of the entire product are very big pluses for me. The software is very simple and straightforward. That is something that is needed right now."
"What I love the most is that StreamSets is very light. It's a containerized application. It's easy to use with Docker. If you are a large organization, it's very easy to use Kubernetes."
"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 UI is user-friendly, it doesn't require any technical know-how and we can navigate to social media or use it more easily."
"The best feature that I really like is the integration."
"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."
"I would like to see better integration with Power BI."
"We have issues with SSIS connectors while extracting data from Excel sources."
"I would like to see more standard components out of the box, such as SFTP, and Data Compression components."
"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."
"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."
"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."
"Sometimes, there are compatibility issues with some features. From time to time, I also face issues when trying to migrate. If I misconfigure things when I use Snapshot, the migration will fail.It can take a long time to migrate huge amounts of data, so it would be nice if that could be faster."
"The creation of the measure in the DAC's model could be improved."
"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."
"The data collector in StreamSets has to be designed properly. For example, a simple database configuration with MySQL DB requires the MySQL Connector to be installed."
"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."
"We've seen a couple of cases where it appears to have a memory leak or a similar problem."
"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."
"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."
"The design experience is the bane of our existence because their documentation is not the best. Even when they update their software, they don't publish the best information on how to update and change your pipeline configuration to make it conform to current best practices. We don't pay for the added support. We use the "freeware version." The user community, as well as the documentation they provide for the standard user, are difficult, at best."
"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."
SSIS is ranked 2nd in Data Integration with 69 reviews while StreamSets is ranked 8th in Data Integration with 24 reviews. SSIS is rated 7.6, while StreamSets is rated 8.4. The top reviewer of SSIS writes "Maintaining the solution and contacting its support team is easy". On the other hand, the top reviewer of StreamSets writes "We no longer need to hire highly skilled data engineers to create and monitor data pipelines". SSIS is most compared with Informatica PowerCenter, Talend Open Studio, IBM InfoSphere DataStage, Oracle Data Integrator (ODI) and AWS Glue, whereas StreamSets is most compared with Fivetran, Informatica PowerCenter, Azure Data Factory, IBM InfoSphere DataStage and webMethods.io Integration. See our SSIS vs. StreamSets 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.