SSIS vs StreamSets comparison

 

Comparison Buyer's Guide

Executive Summary
 

Categories and Ranking

SSIS
Ranking in Data Integration
2nd
Average Rating
7.6
Number of Reviews
69
Ranking in other categories
No ranking in other categories
StreamSets
Ranking in Data Integration
8th
Average Rating
8.4
Number of Reviews
24
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of June 2024, in the Data Integration category, the mindshare of SSIS is 9.8%, down from 10.9% compared to the previous year. The mindshare of StreamSets is 1.6%, up from 1.2% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Data Integration
Unique Categories:
No other categories found
No other categories found
 

Featured Reviews

BobAmy - PeerSpot reviewer
Aug 21, 2023
Robust and does a good job of handling overload conditions
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 believe there are ways to build a model and set variables so that it can be a generic process. In my next system, I would like to have a generic process that would handle all the logging and processing in a model that can be modified and enhanced as the need for a better process, or different statistics to be logged is discovered. I'd want this in a way that the model can be changed and all the processes, with their unique parameters, could all be changed with the model upgraded. I believe they should add some features that help to create the code using a model. This would allow for continuous improvement of the model uses and easy replication of all the different programs that use the model.
Namanya Brian - PeerSpot reviewer
Apr 14, 2023
Data streams and pipelines help our team identify areas for improvement in our solution
One of the things I like is the data pipelines. They have a very good design. Implementing pipelines is very straightforward. It doesn't require any technical skill. We have also integrated it with Kafka messaging and it is not complex to do. It is really so easy to connect or integrate with data interfaces. And moving data into analytics platforms using StreamSets is easy. It doesn't require any coding, meaning your can transfer or move data into data payloads without coding skills. It's a good move, for someone in the beginning, who doesn't have any knowledge because it's quite easy.

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"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."
"There are many good features in this solution including the data fields, database integration, support for SQL views, and the lookups for matching information."
"It is easily scheduled and integrates well with SQL Server and SQL Server Agent jobs."
"I have found its most valuable features to be its package management capabilities and the flexibility it offers in designing workflows."
"It has a drag and drop feature that makes it easy to use. It has a good user experience because it takes into account your most-used tools and they're lined up nicely so you can just drag and drop without looking too far. It also integrates nicely with Microsoft."
"Overall, it's a good product."
"The most important features are it works well and provides self-service BI."
"The initial setup of this solution is very straightforward."
"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 ability to have a good bifurcation rate and fewer mistakes is valuable."
"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 best feature that I really like is the integration."
"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 entire user interface is very simple and the simplicity of creating pipelines is something that I like very much about it. The design experience is very smooth."
"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."
 

Cons

"SSIS is cumbersome despite its drag-and-drop functionality. For example, let's say I have 50 tables with 30 columns. You need to set a data type for each column and table. That's around 1,500 objects. It gets unwieldy adding validation for every column. Previously, SSIS automatically detected the data type, but I think they removed this feature. It would automatically detect if it's an integer, primary key, or foreign key column. You had fewer problems building the model."
"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."
"Tuning using this solution requires extensive expertise to improve performance."
"In terms of its performance, it could be better. That could be something that would be easy and welcomed as an upgrade."
"There is connectivity with other databases, however, this is the most significant issue that has to be addressed."
"I would like to see better technical documentation because many times information is missing."
"We would like the solution to be expanded so that it is available for other platforms than just Microsoft."
"There was also not enough instructions from Microsoft in regards to this application or this technology, which can easily be improved upon."
"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."
"If you use JDBC Lookup, for example, it generally takes a long time to process data."
"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."
"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."
"Using ETL pipelines is a bit complicated and requires some technical aid."
"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."
 

Pricing and Cost Advice

"If you don't want to pay a lot of money, you can go for SSIS, as its open-source version is available. When it comes to licensing, SSIS can be expensive."
"All of my clients have this product included as part of their Microsoft license."
"It would be beneficial if the solution had a less costly cloud offering."
"Our license with SSIS is annual."
"My advice is to look at what your configuration will be because most companies have their own deals with Microsoft."
"SSIS is a cheaper option compared to the cost of other ETL tools."
"SSIS' licensing is a little high, but it gives good value for money."
"I'm not involved in licensing details, but SSIS provides value to our organization by simplifying data management tasks."
"The licensing is expensive, and there are other costs involved too. I know from using the software that you have to buy new features whenever there are new updates, which I don't really like. But initially, it was very good."
"It has a CPU core-based licensing, which works for us and is quite good."
"The overall cost for small and mid-size organizations needs to be better."
"StreamSets is expensive, especially for small businesses."
"The pricing is good, but not the best. They have some customized plans you can opt for."
"Its pricing is pretty much up to the mark. For smaller enterprises, it could be a big price to pay at the initial stage of operations, but the moment you have the Seed B or Seed C funding and you want to scale up your operations and aren't much worried about the funds, at that point in time, you would need a solution that could be scaled."
"The overall cost is very flexible so it is not a burden for our organization... However, the cost should be improved. For small and mid-size organizations it might be a challenge."
"I believe the pricing is not equitable."
report
Use our free recommendation engine to learn which Data Integration solutions are best for your needs.
789,442 professionals have used our research since 2012.
 

Comparison Review

it_user90069 - PeerSpot reviewer
Feb 20, 2014
Informatica PowerCenter vs. Microsoft SSIS - each technology has its advantages but also have similarities
Technology has made it easier for businesses to organize and manipulate data to get a clearer picture of what’s going on with their business. Notably, ETL tools have made managing huge amounts of data significantly easier and faster, boosting many organizations’ business intelligence operations…
 

Top Industries

By visitors reading reviews
Financial Services Firm
18%
Computer Software Company
12%
Government
7%
Healthcare Company
7%
Financial Services Firm
17%
Computer Software Company
13%
Manufacturing Company
8%
Government
7%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
 

Questions from the Community

Which is better - SSIS or Informatica PowerCenter?
SSIS PowerPack is a group of drag and drop connectors for Microsoft SQL Server Integration Services, commonly called SSIS. The collection helps organizations boost productivity with code-free compo...
What do you like most about SSIS?
The product's deployment phase is easy.
What is your experience regarding pricing and costs for SSIS?
If you don't want to pay a lot of money, you can go for SSIS, as its open-source version is available. When it comes to licensing, SSIS can be expensive.
What do you like most about StreamSets?
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 customiz...
What needs improvement with StreamSets?
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 ...
What is your primary use case for StreamSets?
StreamSets is used for data transformation rather than ETL processes. It focuses on transforming data directly from sources without handling the extraction part of the process. The transformed data...
 

Comparisons

 

Also Known As

SQL Server Integration Services
No data available
 

Learn More

Video not available
 

Overview

 

Sample Customers

1. Amazon.com 2. Bank of America 3. Capital One 4. Coca-Cola 5. Dell 6. E*TRADE 7. FedEx 8. Ford Motor Company 9. Google 10. Home Depot 11. IBM 12. Intel 13. JPMorgan Chase 14. Kraft Foods 15. Lockheed Martin 16. McDonald's 17. Microsoft 18. Morgan Stanley 19. Nike 20. Oracle 21. PepsiCo 22. Procter & Gamble 23. Prudential Financial 24. RBC Capital Markets 25. SAP 26. Siemens 27. Sony 28. Toyota 29. UnitedHealth Group 30. Visa 31. Walmart 32. Wells Fargo
Availity, BT Group, Humana, Deluxe, GSK, RingCentral, IBM, Shell, SamTrans, State of Ohio, TalentFulfilled, TechBridge
Find out what your peers are saying about SSIS vs. StreamSets and other solutions. Updated: June 2024.
789,442 professionals have used our research since 2012.