Improving the PATROL HL KM Performance
The P_HISTORY table is created for each database supported by the PATROL HL KM. The P_HISTORY table contains the accumulation of all the history data collected. If the amount of data collected in P_HISTORY grows too large, it can slow the performance of the PATROL HL KM. You can improve the performance of the PATROL HL KM by following these suggestions to keep the P_HISTORY table size manageable:
- Reduce the number of days of history that are stored in P_HISTORY.
- Reduce the number of parameters that store history data in P_HISTORY.
- Periodically archive some of the data in P_HISTORY.
- Recreate the index for P_HISTORY. The necessary SQL statements to accomplish this are listed in the following table.
SQL Statements for Recreating P_HISTORY Index
RDBMS | File |
---|---|
DB2 | HDB2UDBCommCreateTables.psl |
Oracle | HORACommCreateTables.psl |
Microsoft SQL Server | HSYBCommCreateTables.psl |
Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*