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

Elastic Search vs SAS Data Integration Server comparison

 

Comparison Buyer's Guide

Executive Summary

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

Elastic Search
Average Rating
8.2
Reviews Sentiment
6.5
Number of Reviews
96
Ranking in other categories
Indexing and Search (1st), Cloud Data Integration (5th), Search as a Service (1st), Vector Databases (2nd)
SAS Data Integration Server
Average Rating
7.2
Reviews Sentiment
6.5
Number of Reviews
4
Ranking in other categories
Data Integration (40th)
 

Featured Reviews

reviewer2817942 - PeerSpot reviewer
Senior Software Engineer at a consultancy with 11-50 employees
Logging and vector search have transformed observability and empowered reliable ai agents
Elastic Search is not specifically being used for certain purposes. I deploy Elastic Search database on the cloud and use cloud services so that nobody can attack. However, I do not use Elastic Search to resolve attack issues. The basic main purpose of Elastic Search, as of now, I feel it can do more in the AI area. Sometime I saw that when I am developing RAG and have to generate the embeddings, which I call metadata, sometimes it tries to fail. That durability or issue handling should be improved, but apart from that, I did not find anything as of now. As per my use case, whatever I am using seems pretty good. Apart from that, some definitely improvement will be there. One improvement is that it should be faster. Whenever I am searching any logs, it takes much time. For example, if I open my log in Notepad or a similar tool, I can search the text within a second. With Elastic Search, it takes a little bit of time, ten to fifteen seconds. That can be improved. Sometimes, engineers take time to assign when I create a ticket.
NN
Works at a financial services firm with 5,001-10,000 employees
Offloads processes on the server side but needs better installation syntax
One area for improvement is the installation process. Another point could be the syntax, as it sometimes involves using syntax names that are not intuitive. For example, to calculate the difference between two dates, the general syntax in SAS is called the data difference or data net function. However, another name is used, such as NF and INK. Without knowledge of SAS programming, it becomes unclear what these functions mean. It is not good to define function names this way.

Quotes from Members

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

Pros

"The initial installation and setup were straightforward."
"It's a stable solution and we have not had any issues."
"On the subject of pricing, Elastic Search is very cost-efficient, as you can host it on-premises, which would incur zero cost, or take it as a SaaS-based service, where the expenses remain minimal."
"Overall, considering key aspects like cost, learning curve, and data indexing architecture, Elasticsearch is a very good tool."
"The most valuable features are the detection and correlation features."
"The products comes with REST APIs."
"The flexibility and the support for diverse languages that it provides for searching the database are most valuable, and we can use different languages to query the database."
"I appreciate the indexing capabilities and the speed of indexing in their product, which demonstrates how quickly logs are collected and stored."
"A key feature allows us to enhance job performance by offloading processing to the server side, rather than processing on the server itself."
"The solution is very stable."
"The solution offers very good data manipulation and loading."
"The most valuable feature of the solution is its amazing capabilities in regard to data handling."
"The solution offers very good data manipulation and loading."
"A key feature allows us to enhance job performance by offloading processing to the server side, rather than processing on the server itself."
"The solution is very stable."
"A key feature allows us to enhance job performance by offloading processing to the server side, rather than processing on the server itself."
 

Cons

"There is another solution I'm testing which has a 500 record limit when you do a search on Elastic Enterprise Search."
"I would rate the stability a seven out of ten. We faced a few issues."
"This product could be improved with additional security, and the addition of support for machine learning devices."
"They should improve its documentation. Their official documentation is not very informative. They can also improve their technical support. They don't help you much with the customized stuff. They also need to add more visuals. Currently, they have line charts, bar charts, and things like that, and they can add more types of visuals. They should also improve the alerts. They are not very simple to use and are a bit complex. They could add more options to the alerting system."
"I know many customers who lost their data and could not recover it."
"The UI point of view is not very powerful because it is dependent on Kibana."
"Performance improvement could come from skipping background refresh on search idle shards (which is already being addressed in the upcoming seventh version)."
"Machine learning on search needs improvement."
"The initial setup had issues, and even after using it for about one year, it was still not fixed."
"The transform tool has limited access. They should make it more flexible."
"Something that could improve is writing SQL to integration studio because it is not that straightforward. There should be better integration with other software."
"One area for improvement is the installation process."
"The transform tool has limited access. They should make it more flexible."
"So I would like to see improved integration with other software."
"The initial setup had issues, and even after using it for about one year, it was still not fixed."
"The initial setup of SAS Data Integration Server was complex."
 

Pricing and Cost Advice

"There is a free version, and there is also a hosted version for which you have to pay. We're currently using the free version. If things go well, we might go for the paid version."
"This is a free, open source software (FOSS) tool, which means no cost on the front-end. There are no free lunches in this world though. Technical skill to implement and support are costly on the back-end with ELK, whether you train/hire internally or go for premium services from Elastic."
"The tool is not expensive. Its licensing costs are yearly."
"The solution is less expensive than Stackdriver and Grafana."
"We are using the free open-sourced version of this solution."
"I rate Elastic Search's pricing an eight out of ten."
"​The pricing and license model are clear: node-based model."
"We use the free version for some logs, but not extensive use."
"It is an expensive program."
report
Use our free recommendation engine to learn which Cloud Data Integration solutions are best for your needs.
894,738 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
12%
Computer Software Company
9%
Manufacturing Company
9%
Retailer
6%
Financial Services Firm
26%
Construction Company
11%
Comms Service Provider
10%
Computer Software Company
7%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business39
Midsize Enterprise12
Large Enterprise47
No data available
 

Questions from the Community

What is your experience regarding pricing and costs for ELK Elasticsearch?
When it comes to pricing, I think we had to pay AWS approximately 1,000 to 1,200 per month for the overall stack. I am not quite certain about how much Elastic Search costs specifically because I w...
What needs improvement with ELK Elasticsearch?
Elastic Search has many features, including Kibana and Logstash, which we regularly use. However, one downside in our product is cost, as it can be expensive when maintaining multiple shards and in...
What is your primary use case for ELK Elasticsearch?
As a developer, I use Elastic Search in developing one of my applications, basically integrating the back-end with Elastic Search. Our main use case for Elastic Search is for Logstash, which is a s...
What needs improvement with SAS Data Integration Server?
One area for improvement is the installation process. Another point could be the syntax, as it sometimes involves using syntax names that are not intuitive. For example, to calculate the difference...
What is your primary use case for SAS Data Integration Server?
I am involved in the ETR job. My role is focused on executing the ETR job.
What advice do you have for others considering SAS Data Integration Server?
I use it without further details. For example, if I use SAS to connect to a NetEazt database or purchase a shared asset to ODBC, I can connect to any database with ODBC connection support. The over...
 

Also Known As

Elastic Enterprise Search, Swiftype, Elastic Cloud
SAS Enterprise Data Integration Server, Enterprise Data Integration Server
 

Overview

 

Sample Customers

T-Mobile, Adobe, Booking.com, BMW, Telegraph Media Group, Cisco, Karbon, Deezer, NORBr, Labelbox, Fingerprint, Relativity, NHS Hospital, Met Office, Proximus, Go1, Mentat, Bluestone Analytics, Humanz, Hutch, Auchan, Sitecore, Linklaters, Socren, Infotrack, Pfizer, Engadget, Airbus, Grab, Vimeo, Ticketmaster, Asana, Twilio, Blizzard, Comcast, RWE and many others.
Credit Guarantee Corporation, Cr_dito y Cauci‹n, Delaware State Police, Deutsche Lufthansa, Directorate of Economics and Statistics, DSM, Livzon Pharmaceutical Group, Los Angeles County, Miami Herald Media Company, Netherlands Enterprise Agency, New Zealand Ministry of Health, Nippon Paper, West Midlands Police, XS Inc., Zenith Insurance
Find out what your peers are saying about Elastic Search vs. SAS Data Integration Server and other solutions. Updated: April 2026.
894,738 professionals have used our research since 2012.