This excerpt is from DB2 Universal Database V8 Handbook for Windows, UNIX, and Linux, written by Philip Gunning and published by Prentice Hall. Read the entire chapter here.
Regardless of how well a RDBMS performs, the monitoring of SQL statements and resources is required to ensure continued good performance and to identify problem areas. Using the information gathered, adjustments can be made to instance and database configuration parameters, physical design, or SQL to improve performance. The nature of RDBMSs and their implementation, may lead to frequent occurences of events like lock escalation, low bufferpool hit ratios, disk I/O activity, and out-of-space conditions. A DBA group must have a well-established monitoring program to ensure that the database is performing to expectations and that the database will continue to meet performance expectations. This includes having DBA standards and procedures that address monitoring and outline how the DBA organization should conduct monitoring activities.
DB2 provides built-in monitoring capability through the use of snapshot monitoring and event monitoring.
For More Information
- Feedback: E-mail the editor with your thoughts about this tip.
- More tips: Hundreds of free DB2 tips and scripts.
- Tip contest: Have a DB2 tip to offer your fellow DBAs and developers? The best tips submitted will receive a cool prize -- submit your tip today!
- Ask the Experts: Our SQL, database design, Oracle, SQL Server, DB2, metadata, and data warehousing gurus are waiting to answer your toughest questions.
- Forums: Ask your technical DB2 questions--or help out your peers by answering them--in our active forums.
- Best Web Links: DB2 tips, tutorials, and scripts from around the Web.