Vertica Reviews

We use the solution in our data warehouse.

The solution is quick, has good compression data, and is not expensive.

Vertica is user-friendly.

The integration with AI has room for improvement. There is room for better machine learning.

I have been using the solution for 16 years.

The solution is stable.

The solution is easy to scale.

We have seven people using the solution.

The technical support is good.

The initial setup is straightforward. The deployment took four days.

The implementation was completed by a vendor.

The price is reasonable. The solution is free and we pay for the storage.

I give the solution a nine out of ten.

It has improved my organization's functionality and performance. 

You don't have any more dependency on the local store. In order to build the on-prem process for Vertica, you need to make a lot of changes and be picky about choosing your hardware for it. On Eon, you just put it on S3, so you're not paying a penny for the stores anymore. That's the good thing about Eon. 

We are looking for a cheaper deployment for the solution. Although we did a lot of benchmarks, like Redshift. We tried Redshift, it didn't work. It didn't work out for us as well.

I have been using Vertica since 2009.

When you're on-prem, you're always worried about losing your nodes. It was hard to restore especially when you have big data.

Scalability has been amazing. We have seen a lot of improvement. We have developers and we have a production demo. We have hosted clusters for customers, we have deployed customer scope. I can scribe them by petabytes. I can scale them by the number of users. It depends on the customers. For one project we can have 15 to 20 consecutive users, but they deal with petabytes of storage.

Their support is really bad. Maybe Micro Focus has changed but they were not good before. They weren't really responsive. We've never had good support.

I would rate it a three out of ten. I met with them two months ago. They asked why we didn't renew our support. They wasted a lot of our money. We've had really bad experiences with Vertica.

We previously used Oracle and we decided to go for big data. 

The initial setup was straightforward for me, it's not complex at all. You need to be at least a bit of a database administrator and really get certified on Vertica in order to use it. 

My advice to someone considering Vertica is to go for it. 

Nothing is missing. I would rate it a ten out of ten.

The only issues are support and the price. 

In this particular use case, our company is in the media industry and we rely exclusively on Vertica for our analytical and operational reporting requirements.

What I find personally beneficial about Vertica is its ability to scale effortlessly, regardless of the data load. 

In addition, there are several optimization techniques available to fine-tune queries, resulting in faster report generation times compared to any other databases I have worked with.

I appreciate the flexibility offered by Vertica's projections. It allows for modifying the primary projection without altering the tables, which helps to optimize queries without the need to modify the underlying data. 

This feature enables us to fine-tune our queries by modifying different projections, which is highly beneficial.

In my opinion, Vertica's documentation could be improved. Currently, there is not enough documentation available to gain a comprehensive understanding of the platform. Additionally, the community support for Vertica is limited, making it difficult to find assistance or resources when needed.

When it comes to data sharing or desktop usage, Snowflake has an advantage over Vertica and other platforms such as cash. Snowflake provides reporting capabilities to share data between two different accounts, which is not currently available in Vertica. This feature is particularly helpful when sharing data with third-party vendors or clients. However, Vertica does not provide such capabilities, and it is not possible to set up data sharing between two different accounts with just a few clicks, as it is possible in Snowflake.

Vertica is a solution that my team manages.

We have been working with Vertica for a year and a half.

We are currently using version nine, specifically 9.3 or a similar version. We have not yet upgraded to the latest version.

Vertica is always stable.

We have not had any stability issues with Vertica.

Vertica is a scalable solution.

I would rate the scalability an eight or nine out of ten based on the use case that we do.

We are a team that handles operational reporting, and our Vertica implementation is used by thousands of people. However, the team responsible for managing and writing code for Vertica consists of only around ten to twelve people.

I personally have not contacted technical support.

Snowflake is a platform that we use in our company. We have been using this solution for the last six months.

As a user of the platform, I don't engage in Snowflake development directly.

Instead, I use Snowflake as a platform where tables are already set up for me to work with. 

I do not handle any aspects of Snowflake management, such as table creation or sharing configurations, as these are typically set up with minimal clicks. 

My work revolves solely around Vertica, and I am responsible for handling everything related to Vertica.

Regarding the initial setup, I don't have direct involvement in it and cannot provide much comment. It's something that my team handles, and while they found it easy to set up, I don't have many specific insights to share.

Our team handled the deployment, we did it ourselves.

It is not difficult to maintain. 

We have a Database Performance Analyzer (DPA), and we've gained experience over time. I've been handling it for three years now.

I am aware that we have licensed it, but I have no knowledge of its cost. As I am not involved in that area.

We work with both Snowflake and Vertica solutions.

I am exploring the use of both Snowflake and Vertica for various use cases, and I am now evaluating which one would be the best fit for a new use case based on our requirements.

I would recommend using the Database Designer tool to design projections before actively using Vertica, instead of rushing into it like with other databases. Vertica is designed for different use cases, and designing projections beforehand can make things much easier later on. Vertica offers features that we believe people should take advantage of before going into production.

I would rate Vertica an eight out of ten.

We hold financed data on the Vertica database, and clients use the data for reporting and other purposes.

Vertica provides benefits to our customers and helps with their performance.

The most valuable feature is Vertica's performance and the ease of using the database. Also, it is great for partnering with data.

We faced some challenges when trying to use the temporary tables feature. First, we installed Vertica on the AWS cloud and tried to read the data from Bitbucket to Vertica. We were able to read the data, but when we were trying to transform the data and load it into Vertica physical tables, we experienced performance issues.

Regarding additional features, we are unsure if Vertica has updated its features, but we've experienced difficulty in integrating with third-party tools. Clients use multiple technologies and value that integration. Sharing data with third parties should also be improved.

We have been using this solution for two years and are using the latest version.

It is a stable solution.

It is a scalable solution. Initially, we had issues with the scalability, but with the new version, Vertica resolved the issues.

Regarding how many users are using this solution, I do not have a specific number, but our organization is large. So, for example, in a unit with about fifteen clients, two to three clients use Vertica.

I rate this solution a seven out of ten.

Snowflake claims to have many more features than Vertica, but we cannot compare both solutions as we have not used Snowflake. However, if Vertica integrates the use of third-party tools, it would be great and more competitive.

We are using Vertica for dashboards, storing, retrieving, and processing data.

The most valuable feature of Vertica is the unmatchable database performance at a fraction of cost compared to other similar databases.

Vertica can improve automation and documentation.

I have been using Vertica for approximately seven years.

Vertica is stable. They have made improvements in this area but can still improve.

The scalability of Vertica is good.

We have approximately 100 users using this solution.

The support from Vertica is good, they are knowledgeable. However, sometimes there are some challenges when escalating our issue.

I have previously used Teradata long time ago. The price of Teradata was very high and hardware is vendor specific. Vertica can operate on comodity hardware and therefore easily scalable.

The initial setup of Vertica is straightforward.

The price of Vertica is less expensive than some competitors, such as Teradata.

We require one person for maintenance for the 100 users we have.

I rate Vertica an eight out of ten.

Vertica is an excellent data warehouse platform. Its column-oriented architecture makes it a powerful database specialized for data warehouses. Data should be designed around a star schema.

Data is accessed via SQL, which most developers are already familiar with.

Vertica is "catching on" in the software market, so its user knowledge base is gradually increasing.

The price seems reasonable, the product is reliable, and it uses SQL, so developers don't need to learn a new language.

It provides very fast results for analysts running reports. These reports are crucial to help our clients strategize their targeted marketing.

Vertica is relatively new and needs some polish and refinement, but its core functionality is excellent.

Documentation overall is fair to good; but lacks continuity or cohesiveness in places.

Although its knowledge base is increasing, it is still relatively small, making some issues difficult to diagnose without consulting Vertica Tech Support.

Vertica does not have native stored procedures or a native scripting language. Instead, external functions (which can be called from within Vertica) using Java, C++, Linux shell scripting, etc., are supported. This is an unpleasant surprise for many developers, but I feel this has not been a big hindrance in my experience. Complex business logic probably does not belong in a high-performance data warehouse platform. Rather, this should be taken care of during ETL.

I have 3+ years of experience with Vertica.

Deployment had only a few minor issues that one finds with most software.

It has been very stable.

I would give technical support 8 out of 10. They have been responsive, professional and knowledgeable.

• I have used traditional, row-oriented relational databases like SQL Server, Oracle and PostgreSQL for data warehousing. They are optimized for handling transactions, not data warehousing. Vertica is optimized for data warehousing and that was very clearly demonstrated in its ability to scan large amounts of data at high speed. It is also very fast at loading data.
• Vertica uses a distributed, shared-nothing architecture which allows for nodes to be added (or removed) according to need. This is a very scalable architecture which is very difficult to achieve with traditional row-oriented databases.
• Compared to Hadoop, Hive, and Spark, Vertica is much more adept at handling concurrent users.

Installation is recommended for someone familiar with Linux (the only OS available for Vertica). For developers with a Linux background, the issues are very manageable. Documentation is good for the installation, so follow it carefully, step-by-step.

Implementation was in-house. No significant issues were encountered.

ROI is good because Vertica, while not cheap, is a better performer than traditional databases.

• Understand that its strengths depend on a good data warehouse design using a star schema. It was never intended for high volumes of small, randomly distributed inserts, updates and deletes that are typically found in transactional databases.
• It uses column-oriented architecture. It is important to study aspects of this architecture and to implement them and modify them as the database grows in size and more users access the system. This is especially true for projections, run-length encoding, sorting and column ordering. It is important to understand these aspects in order to truly maximize Vertica's performance.

Primary use case is advanced analytics over huge amounts of data. Vertica provides high speed access to high volumes.

Previous to Vertica, some analysis could not be made because of the amount of data needed. Vertica allowed us to take those volumes and process them at a very high speed.

Vertica's most outstanding features are the compression rates achieved and the speed of access of high volume data.

• Support is an area where it could get better. 
• Promotion/marketing must be improved, even though it is a very useful product at very good price, it is not as "popular" as it should be.

One to three years.

Just some issues with clustering, but they were not Vertica's issues.

None.

It could be improved.

Positive

I used Hadoop as the first approach. However, Vertica provided the best of both worlds (huge amounts of data and speed of access for analytics).

Once you got your cluster setup and nodes properly working, it is very simple to set up Vertica.

We did the implementation ourselves.

Huge. We are doing analytics that previously we could not.

We evaluated Exasol, but it came out to be too expensive for the use case.

Do a good volumetric analysis to manage the storage needed.

We are using Vertica for our data warehouse. We run all the ETL and then store the information for the reports which are given to the business team for use for analytical purposes.

Vertica is a columnar database where the query performance is extremely fast and it can be used for real-time integrations for API and other applications. The solution requires zero maintenance which is helpful.

They could improve the integration and some of the features in the cloud version.

I have been using Vertica for approximately six years.

The solution is highly stable.

We have approximately 15 users using this solution in my organization.

Vertica is scalable.

The support is extremely good, they respond immediately and are highly qualified. We interact with them once in a while to have new features explained, sessions understanding, and if we have an issue. We have a good relationship with them.

The installation is not simple, if you go through the documents that are provided you should manage to do it. However, having some technical knowledge would be recommended. 

The time it took to do the implementation was approximately 45 minutes. There is additional software or features that we needed to deploy as part of the migration.

We did the implementation ourselves with a five-person technical team. However, the first time we did the implementation we had support from the Vertica team. They helped us by providing recommendations and best implementation practices.

The pricing could improve, it is a little expensive.

I have evaluated Postgres.

I would recommend this solution to others if it fits their use case. If someone is looking for a data warehouse solution with a fast query process Vertica is a good choice. However, it is different than a relational database. If the choice was between Postgres and Vertica, I would recommend Vertica.

I rate Vertica nine out of ten.