Book Image

HP Vertica Essentials

By : Rishabh Agrawal
Book Image

HP Vertica Essentials

By: Rishabh Agrawal

Overview of this book

<p>With the rise of Massively Parallel Processing (MPP) and NewSQL databases, many users are confused about which MPP technology to opt for. Today, HP Vertica is gaining a lot of traction as a major MPP technology. Vertica's distributed architecture allows fast query processing, and it is a highly fault-tolerant architecture, thus making it one of the most sought-after MPP databases today.</p> <p>HP Vertica Essentials will help you to learn day-to-day administration activities in a step-by-step format. You will start by learning how to install Vertica, followed by its management and monitoring. You will learn about the different backup and restore techniques, including the concept of projections in Vertica. Finally, you will explore the various techniques to improve performance and bulk loading in Vertica. By the end of this book, you will be able to install, manage, and monitor Vertica efficiently.</p>
Table of Contents (13 chapters)

Retaining monitoring information


As discussed earlier, system tables provide a plethora of information regarding various processes running on a database, including queries. However, sometimes we need to store monitoring information. For this, we can employ Data Collector. Information retained by Data Collector is stored on a disk in the DataCollector directory under the Vertica catalog path.

Enabling and disabling Data Collector

To enable or disable Data Collector, we can use the SET_CONFIG_PARAMETER() function. Data Collector is on by default. To disable Data Collector, use the following command:

=> SELECT SET_CONFIG_PARAMETER('EnableDataCollector', '0'); 

Use the following command to enable Data Collector:

=> SELECT SET_CONFIG_PARAMETER('EnableDataCollector', '1');

Viewing the current data retention policy

To view the data retention policy, we can use the GET_DATA_COLLECTOR_POLICY() function. We can replace the component variable with the actual component name, as shown in the following...