Collecting data history

A Netezza Performance Server system can be configured to capture information about user activity such as queries, query plans, table access, column access, session creation, and failed authentication requests. This information is called history data. Database administrators can use history data to gain insight to usage patterns.

History data helps you to answer such questions as:

What are the longest and shortest running queries on the system?
Which queries were submitted by specific users or user groups?
What are typical or the most common types of queries (selects, inserts, deletes, drops, truncates)?
What are the most or least frequently accessed tables or columns?
Which queries were in progress at the time of or just before a system event such as an SPU reset or a DBOS restart?

The system saves history data in a history database. You can create any number of history databases, but only one history databases can be written to at a time.

Note: All dates and times stored in a history database use the GMT timezone.

What type of data is to be collected, which user account is to be used for data collection, how often the collected data is to be loaded to the database, and other criteria are specified by a history configuration. Only one history configuration is active at a time.