No more typing reviews! Try our Samantha, our new voice AI agent.

SAP Replication Server vs StreamSets comparison

Why PeerSpot?
 

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
56th
Average Rating
8.0
Reviews Sentiment
7.0
Number of Reviews
7
Ranking in other categories
Database Development and Management (21st)
StreamSets
Ranking in Data Integration
24th
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 September 2026, in the Data Integration category, the mindshare of SAP Replication Server is 0.9%, up from 0.6% compared to the previous year. The mindshare of StreamSets is 1.1%, down from 1.4% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Data Integration Mindshare Distribution
ProductMindshare (%)
StreamSets1.1%
SAP Replication Server0.9%
Other98.0%
Data Integration
 

Featured Reviews

GagandeepSingh3 - PeerSpot reviewer
Principal Engineer at a tech services company with 1,001-5,000 employees
Good at handling replication, provides cross-database replication but SAP can provide better support for cross-database replication to newer technologies
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 replicate their data from Sybase to a newer technology for data warehousing or other purposes, it would be better if they supported those.
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."
"It's pretty good at handling replication, even under high load. It also provides cross-database replication, for example, from Sybase to Oracle."
"We use this solution for all kinds of communications like RFC, BAPI, IDoc, connecting with the orders, accounts, finance, data stuff, banking, everything."
"This product has a catalog with the location of all the objects which were replicated, and it's very simple to maintain."
"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."
"SAP Replication Server is an application that I consider to be a robust system. It has proven to be highly reliable in my experience."
"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."
"Currently, there is a Hadoop-based infrastructure with several engineers to maintain the data, and now, using SAP Replication Server, it has become automatic and requires fewer people to put data in the data warehouse."
"StreamSets is the leader in the market."
"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."
"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."
"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 ability to have a good bifurcation rate and fewer mistakes is valuable."
"StreamSets has definitely helped us in getting the information into our data lake very quickly, in terms of ingestion, and the most important thing is it has helped us from a resourcing point of view because you can easily upskill a BI or ETL resource without any programming knowledge to work with this, which has drastically reduced the time that we are spending on workloads by 60% to 70% as well as reducing the time spent on ingestion by 30%."
 

Cons

"It's complex. It's necessary to understand a little about infrastructure, like network LAN and VLAN environment."
"Setup was a little complex."
"It's a very expensive solution."
"I would like to see it become mobile-friendly."
"There is a need to improve performance in high transactional processes."
"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."
"There is room for improvement in terms of pricing and faster support."
"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."
"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 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."
"If the data processing in StreamSets takes a long time as compared to the previous solution, then we will reconsider why we use StreamSets."
"There are a few things that can be better."
"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."
"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."
 

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."
"There are two editions, Professional and Enterprise, and there is a free trial. We're using the Professional edition and it is competitively priced."
"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's not so favorable for small companies."
"The pricing is affordable for any business."
"I believe the pricing is not equitable."
"We are running the community version right now, which can be used free of charge."
"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."
"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."
report
Use our free recommendation engine to learn which Data Integration solutions are best for your needs.
911,769 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Construction Company
23%
Financial Services Firm
11%
Outsourcing Company
10%
Retailer
8%
Financial Services Firm
12%
Comms Service Provider
7%
Manufacturing Company
6%
Outsourcing Company
6%
 

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

Ask a question
Earn 20 points
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.
What advice do you have for others considering StreamSets?
If asked, I definitely recommend StreamSets to other users. My overall rating for the solution is nine.
 

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: August 2026.
911,769 professionals have used our research since 2012.