Try our new research platform with insights from 80,000+ expert users

SSIS vs StreamSets comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Dec 19, 2024

Review summaries and opinions

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

Categories and Ranking

SSIS
Ranking in Data Integration
4th
Average Rating
7.6
Reviews Sentiment
6.8
Number of Reviews
73
Ranking in other categories
No ranking in other categories
StreamSets
Ranking in Data Integration
15th
Average Rating
8.4
Reviews Sentiment
7.1
Number of Reviews
20
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of March 2025, in the Data Integration category, the mindshare of SSIS is 8.0%, up from 8.0% compared to the previous year. The mindshare of StreamSets is 1.6%, up from 1.3% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Data Integration
 

Featured Reviews

Sakiru Dosumu - PeerSpot reviewer
Its ability to transform and transport data is extremely valuable
he 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.
Nantabo Jackie - PeerSpot reviewer
Simplified pipelines and helped us break down data silos within our organization
The design experience when implementing batch streaming or ECL pipelines is very easy and straightforward. When we initially attempted to integrate StreamSets with Kafka, it was somewhat challenging until we consulted the documentation, after which it became straightforward. We use StreamSets to move data into modern analytics platforms. Moving the data into modern analytics platforms is still complex. It requires a lot of understanding of logic. StreamSets enables us to build data pipelines without knowing how to code. StreamSets' ability to build data pipelines without requiring us to know complex programming is very important, as it allows us to focus on our projects without spending time writing code. StreamSets' Transformer for Snowflake is simple to use for designing both simple and complex transformation logic. StreamSets' Transformer for Snowflake is extremely important to me as it helps me to connect external data sources and keep my internal workflow organized. Transformer for Snowflake's functionality is a perfect ten out of ten. It is important and cost-effective that Transformer for Snowflake is a serverless engine embedded within the platform, as without this feature, it would be very expensive. This feature helps us to sell at lower budget costs, which would otherwise be at a high cost with other servers. StreamSets has helped improve our organization. StreamSets simplified pipelines for our organization. It is easier to complete a project when we know where and how to start, and working with the team remotely makes it more efficient. This helps us to save time and be more organized when creating data pipelines. Being a structured company that produces reliable resources for our application benefits both our clients and contacts. StreamSets' built-in data drift resilience plays a part in our ETL operations. With prior knowledge, the built-in data drift resilience is very effective, but it can be challenging to implement without the preexisting knowledge. The built-in data drift resilience reduced the time it takes us to fix data drift breakages by 45 percent. StreamSets helped us break down data silos within our organization. The use of StreamSets to break down data silos enabled us to be confident in the services and products we provide, as well as the real-time streaming we offer. This has had a positive impact on our business, as it allowed us to accurately determine the analytics we need to present to stakeholders, clients, and our sources while ensuring that the process is secure and transparent. StreamSets saved us time because anyone can use StreamSets not just developers. We can save around 40 percent of our time. StreamSets' reusable assets helped us reduce workload by around 25 percent. StreamSets saved us money by not having to hire developers with specialized skills. We saved around $2,000 US. StreamSets helped us scale our data operations. Since StreamSets makes it easy to scale our data operations, it enabled us to know exactly where to start at any time. We are aware of the timeline for completing the project, and depending on our familiarity with the software, we can come up with a solution quickly.

Quotes from Members

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

Pros

"Like most Microsoft products, SSIS is user-friendly and easy to use."
"The most valuable feature of SSIS is that you can take data from other servers which are not MS SQL Server or Oracle."
"It is easily scheduled and integrates well with SQL Server and SQL Server Agent jobs."
"The UI is very user-friendly."
"The performance and stability are good."
"The performance is good."
"The data reader is the most valuable feature."
"The script component is very powerful, things that you cannot normally do, is feasible through C#."
"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."
"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."
"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 data drift feature gives us an alert upfront so we know that the data can be ingested. Whatever the schema or data type changes, it lands automatically into the data lake without any intervention from us, but then that information is crucial to fix for downstream pipelines, which process the data into models, like Tableau and Power BI models. This is actually very useful for us. We are already seeing benefits. Our pipelines used to break when there were data drift changes, then we needed to spend about a week fixing it. Right now, we are saving one to two weeks. Though, it depends on the complexity of the pipeline, we are definitely seeing a lot of time being saved."
"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."
"It is really easy to set up and the interface is easy to use."
"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."
"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."
 

Cons

"There was also not enough instructions from Microsoft in regards to this application or this technology, which can easily be improved upon."
"The debugging could be improved because when it came to solving the errors that I've experienced in the past, I've had to look at the documentation for more information."
"SSIS can improve in handling different data sources like Salesforce connectivity, Oracle Cloud's connectivity, etc."
"We have a stability problem because when something works, it works one time. The next time, it doesn't work."
"Integration and the user interface are areas with certain shortcomings that require some improvements."
"It would be nice if you could run SSIS on other environments besides Windows."
"Performance could be better."
"The performance of SSIS could improve when comparing it to Oracle Database."
"Visualization and monitoring need to be improved and refined."
"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."
"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."
"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."
"If you use JDBC Lookup, for example, it generally takes a long time to process data."
"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."
"Sometimes, it is not clear at first how to set up nodes. A site with an explanation of how each node works would be very helpful."
"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."
 

Pricing and Cost Advice

"I'm not involved in licensing details, but SSIS provides value to our organization by simplifying data management tasks."
"SSIS is fairly well-priced - I would rate it at four out of five."
"Based on my experience and understanding, Talend comes out to be a little bit expensive as compared to SSIS. The average cost of having Talend with Talend Management Console is around 72K per region, which is much higher than SSIS. SSIS works very well with Microsoft technologies, and if you have Microsoft technologies, it is not really expensive to have SSIS. If you have SQL Server, SSIS is free."
"It would be beneficial if the solution had a less costly cloud offering."
"t's incredibly cost effective, easy to learn the basics quickly (although like all ETL tools requires the traditional learning curve to get good at) and has an immense user base."
"This solution is included with the MSSQL server package."
"This solution has provided an inexpensive tool, and it is easy to find experienced developers."
"Depending on the arrangement that a certain company has with Microsoft, it may supply the permanent license that is included in the SQL server license, or it may be a time-bound license if it is a partner license or other enterprise license."
"We use the free version. It's great for a public, free release. Our stance is that the paid support model is too expensive to get into. They should honestly reevaluate that."
"StreamSets Data Collector is open source. One can utilize the StreamSets Data Collector, but the Control Hub is the main repository where all the jobs are present. Everything happens in Control Hub."
"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."
"The pricing is too fixed. It should be based on how much data you need to process. Some businesses are not so big that they process a lot of data."
"I believe the pricing is not equitable."
"We are running the community version right now, which can be used free of charge."
"StreamSets is an expensive solution."
"It has a CPU core-based licensing, which works for us and is quite good."
report
Use our free recommendation engine to learn which Data Integration solutions are best for your needs.
842,388 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
8%
Healthcare Company
6%
Financial Services Firm
14%
Computer Software Company
11%
Manufacturing Company
10%
Insurance Company
8%
 

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?
Utilizing SSIS involves no extra charges beyond the SQL Server license. It's an economical choice for my clients.
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
 

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: February 2025.
842,388 professionals have used our research since 2012.