Try our new research platform with insights from 80,000+ expert users

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.6
Number of Reviews
75
Ranking in other categories
Indexing and Search (1st), Cloud Data Integration (9th), Search as a Service (1st), Vector Databases (3rd)
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

Louis McCoy - PeerSpot reviewer
Searches through billions of documents have become impressively fast and consistent
The seamless scalability is something I see as among the best features Elastic Search offers. The speed with which Elastic Search is able to search through all of the documents we place into it is quite remarkable, as we search through 65 billion documents in less than a second in most cases, on a constant consistent basis. I find configuring relevant searches within Elastic Search platform very straightforward. Elastic Search is easily scalable. The customer support for Elastic Search is quite good. I advise others looking into using Elastic Search to think about the future of your platform and where you intend it to be in five years, and based on that, which version of Elastic Search best suits the needs of your platform. Additionally, jump into the AI products first as you're in the planning phase so that as you're filling out your data, the AI products and machine learning products can enrich the data real-time early on in the process, which will save you a lot of time later. The overall performance of the platform, scalability of the platform and other additional features, especially when it comes to AI, really earn the nine.
NN
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 products comes with REST APIs."
"Helps us to store the data in key value pairs and, based on that, we can produce visualisations in Kibana."
"The most valuable feature of Elastic Enterprise Search is the Discovery option for the visualization of logs on a GPU instead of on the server."
"The most valuable features are the data store and the X-pack extension."
"The most valuable feature of Elastic Enterprise Search is the opportunity to search behind and between different logs."
"There's lots of processing power. You can actually just add machines to get more performance if you need to. It's pretty flexible and very easy to add another log. It's not like 'oh, no, it's going to be so much extra data'. That's not a problem for the machine. It can handle it."
"The solution offers good stability."
"We can easily collect all the data and view historical trends using the product. We can view the applications and identify the issues effectively."
"A key feature allows us to enhance job performance by offloading processing to the server side, rather than processing on the server itself."
"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."
"A key feature allows us to enhance job performance by offloading processing to the server side, rather than processing on the server itself."
"The most valuable feature of the solution is its amazing capabilities in regard to data handling."
 

Cons

"Performance improvement could come from skipping background refresh on search idle shards (which is already being addressed in the upcoming seventh version)."
"The solution has quite a steep learning curve. The usability and general user-friendliness could be improved. However, that is kind of typical with products that have a lot of flexibility, or a lot of capabilities. Sometimes having more choices makes things more complex. It makes it difficult to configure it, though. It's kind of a bitter pill that you have to swallow in the beginning and you really have to get through it."
"The pricing of this product needs to be more clear because I cannot understand it when I review the website."
"I don't see improvements at the moment. The current setup is working well for me, and I'm satisfied with it. Integrating with different platforms is also fine, and I'm not recommending any changes or enhancements right now."
"Elastic Search should provide better guides for developers."
"The UI point of view is not very powerful because it is dependent on Kibana."
"There are potential improvements based on our client feedback, like unifying the licensing cost structure."
"It is hard to learn and understand because it is a very big platform. This is the main reason why we still have nothing in production. We have to learn some things before we get there."
"The transform tool has limited access. They should make it more flexible."
"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."
"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."
"So I would like to see improved integration with other software."
 

Pricing and Cost Advice

"The price could be better."
"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."
"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 pricing model is questionable and needs to be addressed because when you would like to have the security they charge per machine."
"The price of Elastic Enterprise is very, very competitive."
"Elastic Search is open-source, but you need to pay for support, which is expensive."
"The solution is free."
"To access all the features available you require both the open source license and the production license."
"It is an expensive program."
report
Use our free recommendation engine to learn which Cloud Data Integration solutions are best for your needs.
869,760 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Computer Software Company
14%
Financial Services Firm
13%
Manufacturing Company
8%
Government
8%
Financial Services Firm
28%
Computer Software Company
8%
Insurance Company
7%
Government
6%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business32
Midsize Enterprise9
Large Enterprise36
No data available
 

Questions from the Community

What do you like most about ELK Elasticsearch?
Logsign provides us with the capability to execute multiple queries according to our requirements. The indexing is very high, making it effective for storing and retrieving logs. The real-time anal...
What is your experience regarding pricing and costs for ELK Elasticsearch?
We used the open-source version of Elasticsearch, which was free.
What needs improvement with ELK Elasticsearch?
We could benefit from refining the machine learning models that we currently use in Elastic Search, along with the possibility to integrate agents, intelligent artificial intelligence, form of agen...
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: September 2025.
869,760 professionals have used our research since 2012.