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
100
Ranking in other categories
Indexing and Search (1st), Cloud Data Integration (5th), Search as a Service (1st), Vector Databases (6th)
SAS Data Integration Server
Average Rating
7.2
Reviews Sentiment
6.5
Number of Reviews
4
Ranking in other categories
Data Integration (41st)
 

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

"Aggregation is faster than querying directly from a database, like Postgres or Vertica, and it's much faster if I want to do aggregation, which allows me to store logs and find anomalies effectively."
"I appreciate the indexing capabilities and the speed of indexing in their product, which demonstrates how quickly logs are collected and stored."
"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."
"The difference in performance of Elastic Search is outstanding; if we compare a traditional database or service for search and index products or, in this case, papers, the difference is outstanding."
"What I like the most about Elastic Search is that I can store my data and search throughout my document."
"Elastic Search, being a vector database, quickly indexes data, allowing for searches based on text and data directly, which I found fascinating."
"Elastic Search is the perfect tool for scalability."
"The stability of Elasticsearch was very high, and I would rate it a ten."
"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."
"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."
 

Cons

"An improvement would be to have an interface that allows easier navigation and tracing of logs."
"I found an issue with Elasticsearch in terms of aggregation. They are good, yet the rules written for this are not really good."
"There is a lack of technical people to develop, implement and optimize equipment operation and web queries."
"Scalability and ROI are the areas they have to improve."
"What they need is to be more transparent about the actual setup of the cluster and the deployment process."
"Elastic Search needs to improve its technical support. It should be customer-friendly and have good support."
"I would rate the stability a seven out of ten. We faced a few issues."
"There is another solution I'm testing which has a 500 record limit when you do a search on Elastic Enterprise Search. That's the only area in which I'm not sure whether it's a limitation on our end in terms of knowledge or a technical limitation from Elastic Enterprise Search. There is another solution we are looking at that rides on Elastic Enterprise Search. And the limit is for any sort of records that you're doing or data analysis you're trying to do, you can only extract 500 records at a time. I know the open-source nature has a lot of limitations, Otherwise, Elastic Enterprise Search is a fantastic solution and I'd recommend it to anyone."
"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."
"One area for improvement is the installation process."
"Something that could improve is writing SQL to integration studio because it is not that straightforward. There should be better integration with other software."
"The transform tool has limited access. They should make it more flexible."
"The initial setup of SAS Data Integration Server was complex."
 

Pricing and Cost Advice

"The cost varies based on factors like usage volume, network load, data storage size, and service utilization. If your usage isn't too extensive, the cost will be lower."
"The price of Elastic Enterprise is very, very competitive."
"We are using the free open-sourced version of this solution."
"The pricing model is questionable and needs to be addressed because when you would like to have the security they charge per machine."
"ELK has been considered as an alternative to Splunk to reduce licensing costs."
"It can move from $10,000 US Dollars per year to any price based on how powerful you need the searches to be and the capacity in terms of storage and process."
"​The pricing and license model are clear: node-based model."
"It can be expensive."
"It is an expensive program."
report
Use our free recommendation engine to learn which Cloud Data Integration solutions are best for your needs.
909,948 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
11%
Manufacturing Company
9%
Computer Software Company
7%
Outsourcing Company
7%
Financial Services Firm
23%
Construction Company
13%
Comms Service Provider
11%
Computer Software Company
7%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business40
Midsize Enterprise12
Large Enterprise50
No data available
 

Questions from the Community

What is your experience regarding pricing and costs for ELK Elasticsearch?
The pricing for Elastic Search is mainly budgeted according to the organization budget, so we take it as a yearly subscription, and that is acceptable since we do get a fair discount when we are ta...
What needs improvement with ELK Elasticsearch?
When we get the logs, it is mostly about how we edit the configurations and how we make changes according to the requirements of our organization. In these cases, the logs sometimes can be a bit in...
What is your primary use case for ELK Elasticsearch?
I am the Elastic Search admin for my organization, and we are using Elastic Search to handle the traffic to GCP. The monitoring of all the clusters and all the deployments are quite good, and compa...
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 Amazon Web Services (AWS), Informatica, Palantir and others in Cloud Data Integration. Updated: August 2026.
909,948 professionals have used our research since 2012.