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

OpenText Analytics Database (Vertica) vs SAP Adaptive Server Enterprise 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

OpenText Analytics Database...
Average Rating
8.2
Reviews Sentiment
6.9
Number of Reviews
90
Ranking in other categories
Data Warehouse (5th), Cloud Data Warehouse (11th)
SAP Adaptive Server Enterprise
Average Rating
8.4
Reviews Sentiment
5.9
Number of Reviews
14
Ranking in other categories
Relational Databases Tools (20th)
 

Mindshare comparison

OpenText Analytics Database (Vertica) and SAP Adaptive Server Enterprise aren’t in the same category and serve different purposes. OpenText Analytics Database (Vertica) is designed for Data Warehouse and holds a mindshare of 5.7%, down 8.4% compared to last year.
SAP Adaptive Server Enterprise, on the other hand, focuses on Relational Databases Tools, holds 1.4% mindshare, up 0.9% since last year.
Data Warehouse Mindshare Distribution
ProductMindshare (%)
OpenText Analytics Database (Vertica)5.7%
Snowflake9.3%
Teradata8.8%
Other76.2%
Data Warehouse
Relational Databases Tools Mindshare Distribution
ProductMindshare (%)
SAP Adaptive Server Enterprise1.4%
Oracle Database10.9%
SQL Server10.7%
Other77.0%
Relational Databases Tools
 

Featured Reviews

JN
consultant at tcs
Data warehousing has transformed reporting performance and now delivers near real-time insights
OpenText Analytics Database (Vertica) is a very powerful analytic database, but like any platform, there are areas where it can improve to make daily work even smoother. Better cloud-native experience is one area for improvement. OpenText Analytics Database (Vertica) was originally designed as an on-premises analytic database and later moved to cloud. Improvement opportunities include more seamless cloud-native features such as auto-scaling, serverless options, and easier cluster management. Competitors such as Snowflake and BigQuery provide more fully managed experiences. Easier UI is another area for improvement. Most administration is currently done by SQL and command line tools. An improvement opportunity would be a more modern web UI for monitoring, workload management, and troubleshooting. Faster ecosystem and community growth is needed. In short, OpenText Analytics Database (Vertica) could improve in areas such as cloud-native capability, modern UI for administration, stronger real-time streaming integration, and growing its ecosystem and community. These enhancements would make it easier to manage and adopt compared to newer cloud-first analytic platforms. From a day-to-day operational perspective, there are a few areas where OpenText Analytics Database (Vertica) could improve to make our work smoother. Smarter automatic projection management is needed with more intelligence, auto projection creation, automatic optimization, and reduced manual testing with better workload management. Right now, monitoring queries often requires system tables and manual analysis. Troubleshooting slow queries takes time. A modern real-time dashboard showing query bottlenecks and resource users would enable quick detection. The impact could be faster issue resolution and less time spent debugging performance. Storage native interaction with modern data tools is also important. In short, from a day-to-day perspective, improvements in automatic projection optimization, better workload monitoring dashboard, easier schema evolution, and stronger modern tool integration would significantly reduce manual tuning effort and improve developer productivity. While OpenText Analytics Database (Vertica) is very powerful, these enhancements would make it more efficient for the analytics team.
reviewer2784705 - PeerSpot reviewer
Senior Advisor at a government with 10,001+ employees
Long term database experience has supported OLTP workloads and delivers reliable cross platform migrations
SAP is not putting money into modernizing SAP Adaptive Server Enterprise. One of the things I discovered on the last project I was on was that they did not incorporate the Intel new instruction set in SAP Adaptive Server Enterprise. Intel has augmented its instruction set referred to as new instructions. They did that to make conversion easier. When you migrate SAP Adaptive Server Enterprise cross-platform, you go through a process where it converts the character set. If you are going from AIX to Linux or from Solaris to Linux, Linux is referred to as Little Endian, while AIX or Solaris are considered Big Endian. This is determined by how the product stores data. The word size of these processors is 32 bits long. If you start numbering from the little end, it is referred to as Little Endian. If you start numbering from the big end, it is called Big Endian. To migrate a SAP Adaptive Server Enterprise database from a Big Endian setup like AIX or Solaris to migrate to a Big Endian setup on an Intel, the operating system determines whether it is Little Endian or Big Endian. When you migrate from Big Endian to Little Endian, the database has to go through a character set conversion, and some of these databases are quite large with gigabytes and gigabytes of data. They have to do a character set conversion to the existing database before they do anything else. The worst part is that you have to rebuild all the indexes when you do that. When you switch endianness of the database, you have to rebuild all the indexes. It will automatically do that for system tables, but for actual user databases, you have to rebuild all your indexes, and it takes a long time. SAP Adaptive Server Enterprise is a relational database and is the predecessor of Microsoft SQL Server. All that functionality that Microsoft SQL Server had came from essentially SAP Adaptive Server Enterprise. The problem with SAP Adaptive Server Enterprise these days is it is not expanding its place in the marketplace or expanding its position in the marketplace. A lot of companies have migrated away from SAP Adaptive Server Enterprise. It works fairly well, but the problem is SAP Adaptive Server Enterprise was architected to be an OLTP engine and is now doing things for larger databases that were not in its original intended purpose. The endianness of the RDBMS is a major impediment to continuing to use SAP Adaptive Server Enterprise. You have a multi-gigabyte database, and it will go through a conversion process in a single-threaded fashion, and then you have to rebuild the indexes. Rebuilding the indexes is lengthy and time-consuming. The part of the conversion process that is concerned with conversion of the character set is single-threaded. You may have eight cores on your machine or virtual machine and only one can be used in the conversion process. There is another problem with the whole thing in that it will sometimes not operate properly. Under certain workloads, SAP Adaptive Server Enterprise will become overwhelmed. When you convert it, it does not operate properly in all circumstances. The root cause of that is that SAP in its desire to save money and desire to orphan the product has not recompiled or redeveloped the product to take advantage of the Intel new instruction set. Other relational databases such as Oracle and Microsoft SQL Server have the same issue to deal with, but with those platforms, they are taking advantage of the new instruction set. There are some additional Intel instruction sets or instructions in their Intel instruction set. With SAP Adaptive Server Enterprise, they did not bother to incorporate support for the new instruction set instructions. In certain circumstances, the database does not operate properly. It is unable to do what it needs to do. If you do your research and go on the internet and see what happens with Oracle or Microsoft SQL Server, what comes back is that it takes 4% longer to perform a lot of the instructions. When you are using the new instruction set, it adds 4% to the runtime of the database.

Quotes from Members

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

Pros

"I enjoy the cybersecurity and backup features."
"It's the fastest database I have ever tested."
"This product has enabled us to keep very large amounts of data at hand for fast querying."
"It maximizes cloud economics with Eon Mode by scaling cluster size to meet variable workload demands."
"Vertica is a great product because customers can compress and code data."
"The most valuable feature of Vertica is the ability to receive large aggregations at a very quick pace. The use case of subclusters is very good."
"Any novice user can tune vertical queries with minimal training (or no training at all)."
"Vertica is very robust and recovers predictably from unexpected infrastructure failures."
"SAP ERP offers us a robust platform where financial stakeholders spend less time collating and sourcing out records and implementing payments."
"The most valuable part of the tool stems from the fact that it is a very cost-efficient product compared to the newer technologies because it needs a very small amount of RAM."
"This is a wonderful database that is, in my opinion, underrated. Users are able to get the most out of my experience by taking advantage of its centralized environment."
"The actual interface is good."
"I like that SAP ASE can match code and the database index to index data in the programming language. There are many other valuable features, such as the table buffer, tuning, and various control agents like dispatcher. SAP ASE can handle many different data types, including views, domains, data elements, structures, objects, and various table types that are most useful in the application. Its modularization technique is also handy."
"In SAP Adaptive Server Enterprise, there are some built-in stored procedures that you can use to fire those commands and get the data in a very systematic manner where you can see the results."
"Sufficient, robust, power DB."
"During the last 20 years, I have never had a stability problem with this product."
 

Cons

"Vertica is relatively new and needs some polish and refinement, but its core functionality is excellent."
"The explain plans are very difficult to read and understand; for one complex query the explain plan I printed out took in excess of 32 A4 pages and no visual tools were available that I could find."
"The documentation of Vertica is an area with shortcomings where improvements are required."
"Node recovery is very inconsistent and impacts performance."
"If your product has lots of concurrent queries this solution is not suitable for you, or you need to implement a cache layer."
"The biggest problem is the cost of cloud deployment."
"OpenText Analytics Database (Vertica) does not have a cloud-based UI that Snowflake has, which features a very good comprehensive GUI for querying and analyzing data."
"Sometimes users write bad queries that has brought down the cluster."
"User interface could be more user friendly."
"Better promotion. Sybase seems little known."
"SAP should refine its debugging method, and the process needs to be a little faster. It should use more Pragmas and fewer pseudocomments. I would like if SAP added more features based on advanced technologies, like artificial intelligence and voice control. The modularization and if-else techniques could also incorporate the latest technology to code and solve complex problems. The SAP Editor should be more elaborative, and it should allow many more types of statements for all uses."
"Because the solution is customized. we do occasionally face unique bugs. There are always some changes that need to be made here and there."
"Cluster features: The Cluster Edition didn't get the same level of reliability as the Enterprise Edition did."
"There could be some improvements in barcode scanning and RFID access."
"The solution is kind-of expensive."
"The overall performance of the product is an area where the tool has certain shortcomings and needs to improve."
 

Pricing and Cost Advice

"Read the fine print carefully."
"The pricing could improve, it is a little expensive."
"Work with a vendor, if possible, and take advantage of more aggressive discounts at mid-fiscal year (April) and fiscal year-end (October).​"
"The price of Vertica is less expensive than some competitors, such as Teradata."
"The pricing depends on the license model because there are several. It depends on the client, but it's cheaper than other solutions. I think it's cheap for all the functionality and robustness. It's not very expensive to deploy."
"It's an expensive product"
"It is fast to purchase through the AWS Marketplace."
"Vertica has a perpetual license, but they are currently trying to convert all those licenses to subscription-based licenses on a yearly basis."
"Price-wise, the product is worth it since one needs very less infrastructure to use it."
"The licensing cost for ASE is pretty low."
"I rate SAP Adaptive Server Enterprise's pricing a six out of ten."
report
Use our free recommendation engine to learn which Data Warehouse solutions are best for your needs.
894,668 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
18%
Computer Software Company
11%
Manufacturing Company
8%
Comms Service Provider
7%
Financial Services Firm
15%
Manufacturing Company
11%
Construction Company
9%
Healthcare Company
7%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business29
Midsize Enterprise23
Large Enterprise43
By reviewers
Company SizeCount
Small Business3
Large Enterprise11
 

Questions from the Community

What is your experience regarding pricing and costs for Vertica?
My experience with pricing, setup cost, and licensing is limited because the organization handled the licensing and pricing as well as the cost setup.
What needs improvement with Vertica?
OpenText Analytics Database (Vertica) is already doing great. There could be a community which could have been much more advanced and more people can be engaged so that any kind of questions, queri...
What is your primary use case for Vertica?
The main use case for OpenText Analytics Database (Vertica) is that we have the Hive and a Hadoop layer for data availability, and Vertica serves as a big data solution. Within a Hive table, OpenTe...
What is your experience regarding pricing and costs for SAP Adaptive Server Enterprise?
From a pricing perspective, I would say the solution is fairly priced. In Oracle, you have two or three databases at most on one machine. In SAP Adaptive Server Enterprise, one machine can have mul...
What needs improvement with SAP Adaptive Server Enterprise?
SAP is not putting money into modernizing SAP Adaptive Server Enterprise. One of the things I discovered on the last project I was on was that they did not incorporate the Intel new instruction set...
What is your primary use case for SAP Adaptive Server Enterprise?
I have worked with SAP Adaptive Server Enterprise, SAP Adaptive Server Enterprise IQ, and Replication Server. I also worked with SQL Anywhere at one point. SAP acquired Sybase at one point, and the...
 

Also Known As

Micro Focus Vertica, HPE Vertica, HPE Vertica on Demand
SAP ASE
 

Overview

 

Sample Customers

Cerner, Game Show Network Game, Guess by Marciano, Supercell, Etsy, Nascar, Empirix, adMarketplace, and Cardlytics.
City of Buenos Aires, ASR Group, Citrix, EarlySense, Usha International Limited, Automotive Resources International (ARI), Takisada-Osaka Co. Ltd., Coelba (Grupo Neoenergia), RZD Russian Railways, National Basketball Association - NBA, TALLY
Find out what your peers are saying about Snowflake Computing, Oracle, Teradata and others in Data Warehouse. Updated: May 2026.
894,668 professionals have used our research since 2012.