Vertica Review

The concurrency got better in this version and we are able to run more queries and load concurrently.

Valuable Features

The compute and processing engine returns the queries fast and let us use our analysis resources in a better utilization.

The concurrency got better in this version and we are able to run more queries and load concurrently.

Improvements to My Organization

We built an internal dashboard using the MicroStrategyto increase visibility to our management and our employees. Also, we built tool to expose the data to our selected partners and users to create better engagement with our platform.

Room for Improvement

  • Loading times for “real time” sources - for example, loading from Spark creates a load on the DB at high scale
  • Connectors to other sources such as Kafka or AWS Kinesis
  • Better monitoring tools
  • Better integration with cloud providers - we were missing some documentation regarding running Vertica on AWS

Use of Solution

We've been using Vertica for a year.

Stability Issues

In case of one HD failure in the cluster, the entire cluster got slower. We feel that it should be able to handle such issues.

Scalability Issues


Customer Service and Technical Support

The support was slow and didn’t provide a solution in most cases. The community proved to be the better source for knowledge and problem solving.

Initial Setup

Pretty straightforward, the installation was simple and we added more nodes easily as we grew.

Pricing, Setup Cost and Licensing

Vertica is pretty expensive, take into account the servers and network costs before committing.

Other Solutions Considered

We evaluated both AWS Redshift and Google BigQuery.

Redshift didn’t fulfill our expectations regarding query latency at high scale (over 60 TB). Regarding BigQuery, we found the pricing structure pretty complex (payment per query and data processed) and harder to control.

Other Advice

Don't plan a production usage on high-scale straight on Vertica, use caching or other buffers between the users and the DB. Get yourself familiar with the DB architecture before planing your model (specifically, make sure you know ROS/WOS and projections). Try to avoid LAP before your schema gets stabilized.

Which version of this solution are you currently using?

**Disclosure: I am a real user, and this review is based on my own experience and opinions.
More Vertica reviews from users
...who work at a Computer Software Company
...who compared it with Teradata
Learn what your peers think about Vertica. Get advice and tips from experienced pros sharing their opinions. Updated: September 2021.
536,114 professionals have used our research since 2012.
Add a Comment
ITCS user