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

Elastic Search vs SAS Access 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 Access
Average Rating
9.0
Reviews Sentiment
7.5
Number of Reviews
3
Ranking in other categories
Data Integration (59th)
 

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.
Robert Heck - PeerSpot reviewer
Co Owner at Hecht und Heck GmbH
The solution is stable, scalable, and flexible
I rate the solution eight out of ten. The number of people required to maintain the solution is dependent on the other applications running. The solution in itself does not require a lot of maintenance. The solution is flexible and I recommend it when you have more complex applications with special requirements.

Quotes from Members

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

Pros

"The product is scalable with good performance."
"The ability to aggregate log and machine data into a searchable index reduces time to identify and isolate issues for an application."
"From a technical point of view, there are no significant issues recalled as Elastic Search has been absolutely awesome for this use case and covers 100% of the needs."
"The solution is quite scalable and this is one of its advantages."
"I appreciate that Elastic Enterprise Search is easy to use and that we have people on our team who are able to manage it effectively."
"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 feature of Elastic Enterprise Search is the opportunity to search behind and between different logs."
"The special text processing features in this solution are very important for me."
"The most valuable feature is you have native access to the external databases."
"The most valuable part of SAS/ACCESS is what it is made for: connecting to remote systems that are not part of your physical SAS environment."
"The most valuable feature is you have native access to the external databases."
"The SAS/ACCESS ability to connect creates an elegant simplicity."
"The most valuable aspect of the solution is the ease of access to the data in those databases."
"The most valuable aspect of the solution is the ease of access to the data in those databases."
 

Cons

"They should improve its documentation. Their official documentation is not very informative."
"This is not exactly a stable solution, which is why we are considering another compatible tool, and whether we go on with Elasticsearch or change it."
"I found an issue with Elasticsearch in terms of aggregation. There is a maximum of 10,000 entries, so the limitation means that if I wanted to analyze certain IP addresses more than 10,000 times, I wouldn't be able to dump or print that information."
"What they need is to be more transparent about the actual setup of the cluster and the deployment process."
"It is hard to learn and understand because it is a very big platform."
"We'd like to see more integration in the future, especially around service desks or other ITSM tools."
"I think the biggest issue we had with Elastic Search was regarding integrations with our multi-factor authentication tool."
"While integrating with tools like agents for ingesting data from sources like firewalls is valuable, I believe prioritizing improvements to the core product would be more beneficial."
"The solution's pricing and licensing are expensive."
"The solution can provide access to the newer databases that come out sooner."
"The primary way that this product can be improved is by adjusting their pricing model."
"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 pricing model needs to be reconsidered and adjusted."
 

Pricing and Cost Advice

"To access all the features available you require both the open source license and the production license."
"I rate Elastic Search's pricing an eight out of ten."
"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 Elasticsearch is fair. It is a more expensive solution, like QRadar. The price for Elasticsearch is not much more than other solutions we have."
"We use the free version for some logs, but not extensive use."
"We are using the Community Edition because Elasticsearch's licensing model is not flexible or suitable for us. They ask for an annual subscription. We also got the development consultancy from Elasticsearch for 60 days or something like that, but they were just trying to do the same trick. That's why we didn't purchase it. We are just using the Community Edition."
"The tool is an open-source product."
"The version of Elastic Enterprise Search I am using is open source which is free. The pricing model should improve for the enterprise version because it is very expensive."
"The solution's pricing and licensing are expensive."
"The pricing model is complex and is based on modular packages as well as the size of the applicable environment."
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%
Construction Company
15%
Financial Services Firm
14%
Comms Service Provider
8%
Manufacturing Company
8%
 

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...
Ask a question
Earn 20 points
 

Comparisons

 

Also Known As

Elastic Enterprise Search, Swiftype, Elastic Cloud
SAS/Access
 

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.
Los Angeles County, West Midlands Police, Credit Guarantee Corporation, Canada Post, Allianz Global Corporate & Specialty
Find out what your peers are saying about Elastic Search vs. SAS Access and other solutions. Updated: April 2026.
894,738 professionals have used our research since 2012.