Vertica Reviews

Analytical features are amazing, the integration is wonderful.

It has helped us escalate, we need information almost real-time.

Documentation, there are functions that are not documented. UDF SDK, I'd like to see a step by step simulator example in a manual. The read-me code is good, however, an example would be great for starters.

3 years

Yes, cluster migration takes time.

Yes, in data streaming ROS containers is a pain to work with.

Not yet.

Customer Service:

It is good, they answer in good time. There are times that they really don't come with a proper answer.

Technical Support:

Decent.

Yes, regular relational databases. We switched for scalability reasons.

In-house.

Yes, Netezza.

I like the new things they are introducing. I want to see more with Python.

Scalability, query speed.

It is the foundation of our new Data Warehouse platform.

Data velocity and manageability.

The utilization/launching project has lasted for a bit more than a year now.

There have been some issues with deleting and updating data from tables.

No

No

Customer Service:

I have not been in contact with their customer service.

Technical Support:

I have not been in contact with their tech support.

We used Oracle but it did not scale well enough

It was straightforward.

I was not involved with the implementation.

Don't know.

The pricing is very flexible

There was a proof of concept for a number of technologies but I wasn't involved in those.

It looks promising.

The speed of Vertica out of the box with the ability it has to perform complex analytics queries. In other databases, information will return in hours or even days while in Vertica it will be finished in minutes or even seconds. This is the best feature it has.

Vertica is in our core technology stack. We are serving reports and dashboard to clients from it. It's very important to us that it fulfills its function correctly and provides us with an advantage over our competitors.

The internal documentation. As a DBA, I really want to understand how its internals works. It needs to handle high concurrency short queries better as Vertica is not handling these well, and we have had to develop our own tool to help us with our dashboard.

I've been using it for five years.

The only thing is that it is very sensitive to network glitches and every time it happens, a node will leave the cluster and we need to re-connect it. Apart from this, the stability is very good.

It is very easy to scale Vertica as you need.

It used to be 10/10 but now it's 8/10. Maybe it's because they were bought by HP which is a big company and the transition is hard.

The last company I worked for shifted from Oracle to Vertica. For our BI queries it's a huge win. Vertica is much better than any other raw store as it is built exactly for complex analytic queries with a huge amount of data.

The earlier version wasn't that good to deploy, but now it's pretty easy to install. If you follow the documentation, you will be OK.

We implemented it in-house. Since it's different than a raw store database, you need to understand the architecture in order to get the most out of Vertica. This means that you will need to design you data model to suit the Vertica architecture otherwise you will get the same performance as the solution you're replacing, or worse. If your implementation is not complex you can just put it in and you will get out of the box improvements, but for complex ones you need to know how Vertica works and build the right design.

It's a great tool but to get the most out of it you will have to design your models to fit it.

We use the product for compressed data store, fast reporting, and self healing analytical data workloads. It also helps with big data ingestions, processing, and reporting.

Bulk loads, batch loads, and micro-batch loads have made it possible for our organization to process near real-time ingestions and faster analytics.

• The tool for performance tuning and recommendations
• Any novice user can tune vertical queries with minimal training (or no training at all).

• It should provide a GUI interface for data management and tuning.
• Monitoring tools need to be lightweight. They should not take up heavy resources of the main server.

One to three years.

The primary use of Vertica is as a data warehouse to perform aggregate and summary reports.

This solution has allowed us to reduce the creation of summarized tables, as the user can perform queries on the fly. It has provided for the faster retrieval of records.

The performance is very good and the aggregate records are fast.

Vertica Auto-Projections reduce the knowledge required by the DBA for tuning performance.

When it is about to reach the maximum storage capacity, it becomes slow.

Before we used Vertica we used another columnar database which turned out to be very unstable and its performance was inconsistent. Vertica turned that around, to the point that it is now our go-to database. We became Vertica partners.

Vertica is a columnar database, this support our developments in analytics, advanced analytics, and our ETL process with large sets of data.

I believe the installation process could be streamlined.

One to three years.

No stability issues.

No scalability issues.

They are very professional and responsive.

See "Improvements to organization," above.

There are some considerations to be evaluated before you start the installation, but the installer does the respective checks so things will function properly. And there are a lot of options.

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.

Infobright and MonetDB.

The technical requirements for the product are really important. The design tool for vertica is the core of the database for performance. Never forget to use it to create projections to optimize the storage compression and response times. Better compression means the 1TB mark takes longer to be reached.

• As it can load a lot of data very quickly, it is very helpful for our organization in managing our VLDB. • It has the lowest cost per TB compared to other DW solutions. • Provides us clustering for our commodity hardware and a good data compression ratio compared to other DW tools I've looked into. • It is very scalable. We didn’t face any problems in terms of installation. • Allows concurrent users access. Our staff can process and send query requests simultaneously -- it responds to all requests very efficiently. • It is very easy to use! It also is good in providing OLAP support to our database system. We can also use traditional SQL queries and tables.

• We can’t use vertica as a transactional database because it is unable to handle lot of transactions. • While copying tables straight across from MYSQL, we observe poor performance. Queries take more time for execution. • Our team is challenged during peak loads because of a lack of work load management options. • It doesn’t offer us any configuration options for reducing the size of our database system and limiting our resource usage.

We are using Vertica because it is a fast and reliable data warehousing tool and provides us a very good data compression ratio. It is cheap in terms of overall cost per TB and also requires less human resource for maintenance and tuning. Vertica I have been told has improved cloud deployment capabilities on any infrastructure.

• Massive data ingestion performance
• Performance
• SQL standard query engine

DWH core platform is based on it

• Machine learning implementations
• Support for Cloud based environments like Google Compute Engine

3 years