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

SAP Replication Server 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

SAP Replication Server
Ranking in Data Integration
41st
Average Rating
8.0
Reviews Sentiment
7.0
Number of Reviews
7
Ranking in other categories
Database Development and Management (20th)
StreamSets
Ranking in Data Integration
21st
Average Rating
8.4
Reviews Sentiment
7.0
Number of Reviews
21
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of February 2026, in the Data Integration category, the mindshare of SAP Replication Server is 0.8%, up from 0.5% compared to the previous year. The mindshare of StreamSets is 1.2%, down from 1.6% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Data Integration Market Share Distribution
ProductMarket Share (%)
StreamSets1.2%
SAP Replication Server0.8%
Other98.0%
Data Integration
 

Featured Reviews

reviewer1834542 - PeerSpot reviewer
Finance Business Process Improvement, Transformation and Project Management at a consultancy with self employed
Eliminates replication and allows you to use only one database, speeding up performance and reducing amount of storage
The private solution is expensive. If you're in a situation where you're paying IBM or AWS or somebody just to host you specifically, you're paying people to run it and you're taking care of all the upgrades. As a company, you're either hiring or paying an outsourcer to do that, and you have to manage it, keep up with the updates to the hardware, software, and the operating system. It's very expensive because there's a lot to control and take care of.
SS
Enterprise Solutions Architect at a energy/utilities company with 1,001-5,000 employees
Enables effective batch loading with visual interface and enterprise support
One issue I observed with StreamSets is that the memory runs out quickly when processing large volumes of data. Because of this memory issue, we have to upgrade our EC2 boxes in the Amazon AWS infrastructure. I had to switch to a new EC2 box, even though the processor was not fully utilized. It would be beneficial if StreamSets addressed any potential memory leak issues to prevent unnecessary upgrades. Additionally, it would be a great enhancement if StreamSets could produce a lineage graph to visualize how the data has passed through the system.

Quotes from Members

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

Pros

"We can customize any workflow and we also like the business domain modeling that can be done."
"SAP is renovating different things. We are using external tools to connect as of now. It is going well, and now the new generation integration platforms are going to be pretty easy."
"It's pretty good at handling replication, even under high load. It also provides cross-database replication, for example, from Sybase to Oracle."
"It speeds up the performance in terms of how fast you are able to access the data, look at it, get it reported to you, and send it to somebody. It also reduces the amount of storage."
"SAP Replication Server is an application that I consider to be a robust system. It has proven to be highly reliable in my experience."
"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."
"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."
"The most valuable features are the option of integration with a variety of protocols, languages, and origins."
"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."
"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."
"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."
"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."
"StreamSets is the leader in the market."
 

Cons

"I would like to see it become mobile-friendly."
"If someone wants to replicate their data from Sybase to a newer technology for data warehousing or other purposes, it would be better if they supported those."
"The private solution is expensive. If you're in a situation where you're paying IBM or AWS or somebody just to host you specifically, you're paying people to run it and you're taking care of all the upgrades."
"Improvement is a never ending story, and HANA is doing some improvements. We are able to adopt that, and we have to do it by integration with HANA. They are very major changes that we need to see."
"There is room for improvement in terms of pricing and faster support."
"The documentation is inadequate and has room for improvement because the technical support does not regularly update their documentation or the knowledge base."
"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."
"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."
"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."
"One issue I observed with StreamSets is that the memory runs out quickly when processing large volumes of data. Because of this memory issue, we have to upgrade our EC2 boxes in the Amazon AWS infrastructure."
"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."
"We create pipelines or jobs in StreamSets Control Hub. It is a great feature, but if there is a way to have a folder structure or organize the pipelines and jobs in Control Hub, it would be great. I submitted a ticket for this some time back."
"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."
 

Pricing and Cost Advice

"It's a very expensive solution."
"You can pick one of the hosted cloud services as opposed to owning it and doing it yourself. Your cost of ownership on the hardware, the data storage, and the maintenance all go down. It depends on what service you use."
"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."
"There are different versions of the product. One is the corporate license version, and the other one is the open-source or free version. I have been using the corporate license version, but they have recently launched a new open-source version so that anybody can create an account and use it. The licensing cost varies from customer to customer. I don't have a lot of input on that. It is taken care of by PMO, and they seem fine with its pricing model. It is being used enterprise-wide. They seem to have got a good deal for StreamSets."
"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."
"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."
"It has a CPU core-based licensing, which works for us and is quite good."
"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."
"We are running the community version right now, which can be used free of charge."
"There are two editions, Professional and Enterprise, and there is a free trial. We're using the Professional edition and it is competitively priced."
report
Use our free recommendation engine to learn which Data Integration solutions are best for your needs.
881,565 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Retailer
11%
Financial Services Firm
10%
Energy/Utilities Company
8%
Computer Software Company
8%
Insurance Company
8%
Financial Services Firm
8%
Manufacturing Company
8%
Computer Software Company
7%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business2
Midsize Enterprise1
Large Enterprise5
By reviewers
Company SizeCount
Small Business9
Midsize Enterprise2
Large Enterprise11
 

Questions from the Community

What needs improvement with SAP Replication Server?
SAP can provide better support for cross-database replication to newer technologies. The product supports Oracle, but I am not aware of what other technologies it supports. If someone wants to repl...
What is your primary use case for SAP Replication Server?
It's basically to transfer data from one server to another. It's used for this purpose.
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?
One issue I observed with StreamSets is that the memory runs out quickly when processing large volumes of data. Because of this memory issue, we have to upgrade our EC2 boxes in the Amazon AWS infr...
What is your primary use case for StreamSets?
We are using StreamSets for batch loading.
 

Also Known As

Sybase Replication Server
No data available
 

Overview

 

Sample Customers

Medtronic, Cirque du Soleil, Antarc, B&G Manufacturing, EarlySense, eBay, Ferrero, James Austin Company, Lenovo, Sagem, RAK Ceramics, Vodafone
Availity, BT Group, Humana, Deluxe, GSK, RingCentral, IBM, Shell, SamTrans, State of Ohio, TalentFulfilled, TechBridge
Find out what your peers are saying about SAP Replication Server vs. StreamSets and other solutions. Updated: January 2026.
881,565 professionals have used our research since 2012.