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

Apache HBase vs OpenText Analytics Database (Vertica) comparison

Why PeerSpot?
 

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

Apache HBase
Average Rating
7.2
Reviews Sentiment
5.1
Number of Reviews
4
Ranking in other categories
NoSQL Databases (13th)
OpenText Analytics Database...
Average Rating
8.2
Reviews Sentiment
6.9
Number of Reviews
90
Ranking in other categories
Data Warehouse (6th), Cloud Data Warehouse (11th)
 

Featured Reviews

Ephrem Sisay - PeerSpot reviewer
Senior Software Engineer at a computer software company with 501-1,000 employees
In-memory processing and integration capabilities have optimized query performance
Apache HBase could be improved by optimizing the integration with Apache Phoenix; sometimes the abstraction and lookup jobs lead to issues when there are too many requests. Resource optimization isn't always as successful as it should be, which can cause some query and lookup jobs to fail. For instance, during eligibility checks for credit, if there are many requests on the database, it might fail, and after such a failure, it doesn't allow us to run queries from the moment they stop. If there could be optimization to require less resource usage and allow those jobs and queries to pick up from where they stopped, that would be a great addition to the tool.
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.

Quotes from Members

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

Pros

"The most valuable part is the column family structure."
"The best features of Apache HBase include being embedded, making it very fast; when it's linking, it operates with virtually no delay, and all of the queries are very fast too due to some internal optimization which makes it very sufficient and efficient."
"Apache HBase is a database used for data storage."
"The in-memory processing lets us optimize our queries and helps us run concurrent queries and other jobs such as the lookup jobs we always use Apache HBase for."
"We are using Vertica because it is a fast and reliable data warehousing tool and provides us a very good data compression ratio."
"The product's initial setup phase is extremely simple."
"The solution is quick, has good compression data, and is not expensive."
"I don't need any special hardware. I can use commodity hardware, which is nice to have in a commercial solution."
"A SQL-based compute platform like Vertica enables far less human overhead in operations and analytics."
"Vertica stands top among its peers in the MPP world, delivering unparalleled speed and performance in query response time."
"We are also opening new areas of business and potential new revenue streams using Vertica's analytic functions, most notably geospatial, where we are able to run billions of comparisons of lat/long point locations against polygon and point/radius locations in seconds. ​"
"The most valuable feature is Vertica's performance and the ease of using the database."
 

Cons

"I don't like using Apache HBase to store huge amounts of data because of many performance issues."
"We've seen performance issues."
"The setup of Apache HBase needs a lot of time, and the linkage is not the program itself, but the activation and connecting to the NYPD engine always takes considerable time."
"Apache HBase could be improved by optimizing the integration with Apache Phoenix; sometimes the abstraction and lookup jobs lead to issues when there are too many requests."
"Vertica is relatively new and needs some polish and refinement, but its core functionality is excellent."
"There have been some issues with deleting and updating data from tables."
"We can’t use Vertica as a transactional database because it is unable to handle lot of transactions."
"Very bad support, I would rate it two out of 10."
"In our company, we have faced difficulties in scaling the solution for certain use cases."
"Support is an area where it could get better."
"Projections take up a lot of space and hence, compression can be improved."
"They could improve on customer service."
 

Pricing and Cost Advice

Information not available
"The solution is free and we pay for the storage."
"The first TB is free and you can use all the Vertica features. After 1TB you have to pay for licensing. The product is worth it, but be aware of this condition, and plan. The compression ratio is explained in the documentation."
"The pricing and licensing depend on the size of your environment and the zone where you want to implement."
"I am aware that we have licensed it, but I have no knowledge of its cost."
"It's free up to three nodes and 1TB, and then get in contact with their sales guys."
"Work with a vendor, if possible, and take advantage of more aggressive discounts at mid-fiscal year (April) and fiscal year-end (October).​"
"Read the fine print carefully."
"The price could be cheaper and it is best to negotiate the price."
report
Use our free recommendation engine to learn which NoSQL Databases solutions are best for your needs.
915,341 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
18%
Comms Service Provider
14%
University
8%
Construction Company
7%
Financial Services Firm
14%
Outsourcing Company
14%
Manufacturing Company
10%
Comms Service Provider
8%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
No data available
By reviewers
Company SizeCount
Small Business29
Midsize Enterprise23
Large Enterprise43
 

Questions from the Community

What needs improvement with Apache HBase?
Apache HBase could be improved by optimizing the integration with Apache Phoenix; sometimes the abstraction and lookup jobs lead to issues when there are too many requests. Resource optimization is...
What advice do you have for others considering Apache HBase?
I'm working for a corporate that uses Apache HBase for their Big Data platform and I'm a Big Data engineer there. We're using a version of Apache HBase that is compatible with the other Big Data to...
What is your primary use case for Apache HBase?
We are using Apache HBase as a lookup database for queries that require doing lookups on customer data and eligibility checks for different kinds of customers. The customer data is stored in the Ap...
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...
 

Also Known As

HBase
Micro Focus Vertica, HPE Vertica, HPE Vertica on Demand
 

Overview

 

Sample Customers

Bloomberg, Wells Fargo, Apple, Capital One, NVIDIA
Cerner, Game Show Network Game, Guess by Marciano, Supercell, Etsy, Nascar, Empirix, adMarketplace, and Cardlytics.
Find out what your peers are saying about Microsoft, MongoDB, Redis and others in NoSQL Databases. Updated: September 2026.
915,341 professionals have used our research since 2012.