Vertica Review

Our typical run time for a query is now measured in seconds not hours.

What is most valuable?

Two of them:

  • The core feature, meaning their highly efficient columnar file format and execution engine along with a great coverage of ANSI SQL, provides our analysts with a highly expressive and performing platform.
  • The extensibility and efficiency provided by their C++ SDK.

How has it helped my organization?

Before Vertica, we used a combination of sharded RDBMSs and Hive: the typical runtime for a query was in the hours. It's now in the seconds, with way
more data than then (we're talking hundreds of terabytes).

What needs improvement?

Whatever's out, the core is not always as great as the engine, especially their first version. That's true, for example, for the Kafka or Hadoop integration.
But they're getting better release after release.

For how long have I used the solution?

Four years.

What do I think about the stability of the solution?

Vertica's code, being designed to use the hardware at its maximum, is very sensitive to low level changes such as kernel bumps or GLibC upgrades. It's also important to do tests on the storage layer (RAID controller + disks).

What do I think about the scalability of the solution?

The default layout (all nodes running spread) introduces latencies in query planning when you reach about 60 nodes, in our experience. Switching to a large cluster (one control node per rack) would be advised, way before reaching the 128 nodes hard limit.

How are customer service and technical support?

It's really great. One of the best I had to deal with. They also assisted us during the development phase of the custom components we've designed.

Which solution did I use previously and why did I switch?

Not really in the same area (MPP databases). However, we ran benchmarks back then against a bunch of competitors and Vertica was one of the fastest, while
being relatively cheap and able to accommodate our hardware.

How was the initial setup?

The setup per se was pretty straightforward. However, it took us some time to design the most efficient loading pattern from Hadoop.

What's my experience with pricing, setup cost, and licensing?

Nothing to advise really; try it out first, it's free up to three nodes and 1TB, and then get in contact with their sales guys.

Which other solutions did I evaluate?

We did evaluate mostly SAP HANA and SQL Server PDW back in 2013, along with a bunch of OSS solutions.

What other advice do I have?

If you plan to use Vertica for different workloads (in term of IO patterns, query frequency, dataset structure) plan to split your clusters: the mother of all cluster patterns becomes quite difficult to manage at some point. We today have around 20 clusters for different usages.

**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: May 2021.
511,607 professionals have used our research since 2012.
Add a Comment
ITCS user