Fast with some limitations
Updated December 29, 2016

Fast with some limitations

Anonymous | TrustRadius Reviewer
Score 7 out of 10
Vetted Review
Verified User

Overall Satisfaction with Vertica

We use Vertica as an analytics database for reporting, ad-hoc queries, regular reporting and more in-depth analyses. It is primarily used for querying by the analytics org and indirectly, through Looker, by the entire company. Vertica is most helpful because of its speed. Ad-hoc queries and analyses can be completed relatively quickly.
  • Speed. Even with tables with 20 Billion+ rows, Vertica performs reasonably well.
  • Analytical functions. Some of the advanced functions in Vertica enable/facilitate interesting and complex analyses.
  • Reliability. We never run into reliability issues with Vertica.
  • Data size limitations. Beyond a certain threshold Vertica breaks down. Because of this, we are not able to put all our data in Vertica and have to resort to Scala/Hive on Hadoop.
  • Pricing: Vertica can get pretty expensive with large data sizes.
  • Speed: Queries could always be faster!
  • Limited options for querying clients: We primarily use Vertica from our terminals. Options for GUI clients are ugly and outdated. Using the terminal for querying is sometimes annoying, with problems like showing query runtime only in milliseconds and not being able to change it, columns being hard to read when there are more columns than the display space etc.
  • The ROI on fast, interactive querying is very high.
  • Table size limitations force us to use other tools, slowing things down.
  • Relatively expensive pricing forces us to regularly upgrade our Vertica subscription and database. Each upgrade leads to a downtime of a few days.
Presto would be a good solution that would be less expensive and would also allow direct querying of all our data on Hadoop while maintaining good speed.
It is appropriate for interactive querying. It is not appropriate for complete storage of all your data for bigger companies.