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
30th
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 November 2026, in the Data Integration category, the mindshare of SAP Replication Server is 1.0%, up from 0.7% compared to the previous year. The mindshare of StreamSets is 1.1%, down from 1.3% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Data Integration Mindshare Distribution
ProductMindshare (%)
StreamSets1.1%
SAP Replication Server1.0%
Other97.9%
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."
"The most valuable thing about this product is that it replicates data between SAP databases (ASE to IQ) very successfully."
"We use this solution for all kinds of communications like RFC, BAPI, IDoc, connecting with the orders, accounts, finance, data stuff, banking, everything."
"SAP Replication Server is an application that I consider to be a robust system. It has proven to be highly reliable in my experience."
"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."
"This product has a catalog with the location of all the objects which were replicated, and it's very simple to maintain."
"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."
"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."
"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 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."
"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 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%."
"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."
"The most valuable features are the option of integration with a variety of protocols, languages, and origins."
 

Cons

"I would like to see it become mobile-friendly."
"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."
"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."
"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."
"It's complex. It's necessary to understand a little about infrastructure, like network LAN and VLAN environment."
"Setup was a little complex."
"There is room for improvement in terms of pricing and faster support."
"If the data processing in StreamSets takes a long time as compared to the previous solution, then we will reconsider why we use StreamSets."
"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."
"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."
"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."
"One thing that I would like to add is the ability to manually enter data. The way the solution currently works is we don't have the option to manually change the data at any point in time. Being able to do that will allow us to do everything that we want to do with our data. Sometimes, we need to manually manipulate the data to make it more accurate in case our prior bifurcation filters are not good. If we have the option to manually enter the data or make the exact iterations on the data set, that would be a good thing."
"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."
"If you use JDBC Lookup, for example, it generally takes a long time to process data."
"The documentation is inadequate and has room for improvement because the technical support does not regularly update their documentation or the knowledge base."
 

Pricing and Cost Advice

"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."
"It's a very expensive solution."
"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."
"The pricing is affordable for any business."
"StreamSets is an expensive solution."
"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."
"I believe the pricing is not equitable."
"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 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."
"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."
report
Use our free recommendation engine to learn which Data Integration solutions are best for your needs.
921,148 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Construction Company
21%
Comms Service Provider
14%
Outsourcing Company
10%
Financial Services Firm
9%
Financial Services Firm
10%
Outsourcing Company
9%
Comms Service Provider
9%
Healthcare 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: October 2026.
921,148 professionals have used our research since 2012.