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.
- 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?
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.