Recommended Monitoring Activities
A quick list of monitoring activities that offer a foundation for workload management follows:
The DBC.Acctg table is the underlying table for the AMPUsage view, and captures data about user usage of CPU and I/O for each AMP. Heavy resource consumers over time, skewed work, and application usage trends can be identified.
The ResUsage tables report on the aggregate effect of all user requests on various system components over time, and can identify bottlenecks and capacity issues. See Resource Usage Macros and Tables for details on all ResUsage data and macros.
Lock Viewer is essential for identifying locking conflicts.
The Database Query Log records details on queries run, including arrival rates, response times, objects accessed, and SQL statements performed. See Database Administration and SQL Data Definition Language for more information about Query Logging.
Priority Scheduler monitor output information shows comparative CPU usage across Priority Scheduler groups. This monitor output should be collected daily, minimally at a 5 or 10-minute interval, then summarized or charted. See Utilities: Volume 2 (L-Z) for more information about the Priority Scheduler utility.
You should use canary queries with tactical query applications. See “Using Canary Queries” on page 915 for more information about this monitoring technique.