myVertica  

Vertica Blog

query

The Life of a Query, According to Henry Ford

While Henry Ford did not in fact develop or even patent the modern assembly line (that credit goes to Ransom E. Olds), he relied heavily on the process for automobile production.

Redesigning Projections for Query Optimization

When you submit a query to Vertica, the Vertica query optimizer automatically assembles a query plan, which consists of a set of operations to compute the requested result. Depending on the properties of the projections defined in your database, the query optimizer can choose faster and more efficient operations. Thus, it’s important to recognize what you can do to optimize your projections to improve query performance

Troubleshooting Vertica Query Performance with System Tables

Do you want to learn how to troubleshoot your query performance issues?  We’ve got you covered. Just attend the Query Performance Tuning and Troubleshooting Issues session at HPE Vertica’s Big Data Conference.

Do You Need to Put Your Query on a Budget?

Before we scare you away with the word “budget,” rest assured that after reading this blog, you won’t have to give up your favorite activities or sell your car. What you will be able to do is understand how Vertica resource pool parameters affect query budget.

Looking Under the Hood at Vertica Queries

When you submit a query to Vertica, you want it to execute as quickly and efficiently as possible. The query optimizer creates a plan that is designed to do just that. The directives in the query plan determine your query’s run-time performance and resource consumption, but the properties of your projections and the system parameters also impact the query’s performance.

 

Tell the Optimizer You Have a Better Plan

You’re upgrading your database and some query appears to execute less efficiently than before. What can you do? HPE Vertica addresses this concern in Vertica 7.2 with directed queries

Using JDBC Routable Query API for High Concurrency and High Throughput

Does your organization use high-volume short requests that return a small number of results on a single node? Do you deal with low latency and high concurrency queries, and want to achieve high throughput? You could benefit by using the HP Vertica JDBC Routable Query API that uses fewer system resources than distributed queries.