We performed a comparison between SAP Data Services and SAS Access based on real PeerSpot user reviews.
Find out in this report how the two Data Integration Tools solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI.
"In StreamSets, everything is in one place."
"It is really easy to set up and the interface is easy to use."
"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 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."
"It is a very powerful, modern data analytics solution, in which you can integrate a large volume of data from different sources. It integrates all of the data and you can design, create, and monitor pipelines according to your requirements. It is an all-in-one day data ops solution."
"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."
"It's easy to understand and deploy. It's easy to create new applications, and depending on the complexity of the application, it is easy to deploy the new requirements."
"I like how SAP Data Services links reporting and data integration. That's what's most interesting. You also have the opportunity to leverage the power of the Data Services server."
"You can always manipulate a lot of things as long as you have the skill level."
"The most valuable feature is the ETL functionality."
"Its integration capabilities and the data migration capabilities are the most valuable. It is very good for SAP and non-SAP tools. It has very good integration with SAP, but it also has the capabilities to connect to other systems. We find it very helpful and stable."
"The BA reporting tools, such as Data Services, and ETL tool in SAP Data Services are the most valuable. When we had in-memory requirements, we used HANA. HANA is most preferably for most the customers for in-memory. SAP is the first company that created the in-memory concept."
"The API tool in this product is very valuable; it is very easy to onboard and use."
"The basic functionality is quite good as is the basic logic and data information."
"The most valuable aspect of the solution is the ease of access to the data in those databases."
"The most valuable feature is you have native access to the external databases."
"The logging mechanism could be improved. If I am working on a pipeline, then create a job out of it and it is running, it will generate constant logs. So, the logging mechanism could be simplified. Now, it is a bit difficult to understand and filter the logs. It takes some time."
"If you use JDBC Lookup, for example, it generally takes a long time to process data."
"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."
"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."
"Sometimes, when we have large amounts of data that is very efficiently stored in Hadoop or Kafka, it is not very efficient to run it through StreamSets, due to the lack of efficiency or the resources that StreamSets is using."
"We've seen a couple of cases where it appears to have a memory leak or a similar problem."
"Data Services SAP is lacking in sources and target databases compared to Informatica. SAP Data Services should have more connectivity."
"The skillset of data engineers matters a bit to use all the functionality of this solution. Otherwise, the delivery speed won't be faster."
"We would like the different tools offered within this solution to be available as standalone entities, rather than having to purchase the entire package when we only require a few features."
"They could make it easier to work with web services."
"At the integration level, there could be certain set of improvement to connect to various other systems."
"It's an ETL that is very good with relational databases but not as good with files and semi-structured files."
"I want some more business intelligence applications. People need to know more and more about data, including the transformation rules, etc. Informatica is a better product for data cataloging. SAP should update the data catalog."
"Source code control is another headache. When your source code base gets too large, managing the source code becomes cumbersome."
"I can't really recall any missing feature or general improvement that is needed. We don't really add too many new kinds of databases and therefore our needs are already met."
"The solution can provide access to the newer databases that come out sooner."
SAP Data Services is ranked 7th in Data Integration Tools with 11 reviews while SAS Access is ranked 38th in Data Integration Tools with 2 reviews. SAP Data Services is rated 8.0, while SAS Access is rated 8.6. The top reviewer of SAP Data Services writes "It's a powerful tool that does a lot, but it has its annoyances". On the other hand, the top reviewer of SAS Access writes "Great for database access with an easy installation and good scalability". SAP Data Services is most compared with Azure Data Factory, SSIS, Informatica PowerCenter, SAP Process Orchestration and Palantir Foundry, whereas SAS Access is most compared with Toad Data Point, SSIS, Mule Anypoint Platform, SAP Process Orchestration and Informatica PowerCenter.
See our list of best Data Integration Tools vendors and best Cloud Data Integration vendors.
We monitor all Data Integration Tools reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.
