Vertica Review

Lack of Stored Procedures, packages, triggers make things difficult for developers

What is most valuable?

Partition and join back to node are easy and simple for DBAs.

DBAs don’t need to add a partition every month/quarter like with other DBs.

What needs improvement?

There are a lot of limitations within this product and it makes things extremely hard for developers. It lacks Stored Procedure, packages, and triggers like other RDBMs.

For how long have I used the solution?

One to three years.

What do I think about the stability of the solution?

Yes, we have encountered issues with Projections and performance.

How are customer service and technical support?

Very bad support, I would rate it two out of 10.

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

We use DB2, Oracle , MySQL, MSSQL. We switched to Vertica to explore it for  future projects.

How was the initial setup?

Easy setup. Much easier than setting up Oracle RAC.

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

Licensing is based on size of the database.

Which other solutions did I evaluate?

They did a good PoC and we were impressed with Vertica. However, when we implemented, it was nightmare with bad support.

What other advice do I have?

My advice regarding this product is a definite "no", due to bad support.

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