 DB2 Workload Management
Today, for both strategic and financial reasons, many businesses are consolidating multiple individual data servers onto a single shared data server. As each new data server is merged, it potentially adds a very different type of workload to the mix with different system interactions. The consolidated server must now support a variety of different, concurrent workloads. Good workload management practices are critical to meeting business commitments in such an environment.
When your database system encounters performance degradation due to the different, and sometimes conflicting, resource demands from the work being executed on it, then you need DB2 workload manager to help you prevent, detect, and resolve these conflicts.
This paper introduces you to the current best practices for DB2 workload manager on your DB2 Version 9.5 for Linux, UNIX, and Windows data server which can be used to help you meet your business objectives for the work being executed on DB2 data servers. The best practices presented here are based on IBM field experience in benchmark and proof-of-concept exercises as well as feedback from customer adoptions of DB2 Version 9.5.
There are three sections to this paper covering:
- Best practices in design
- Best practices in implementation
- Best practices in monitoring
There are also appendices in this paper that provide you with more in-depth information and guidance such as:
- A specific scenario that shows you how to help meet your business priorities with DB2 workload manager in a data warehouse environment
- An example script to use with the AIX® Workload Manager to achieve dynamic processor allocation while using hard maximum limits on CPU use
- Guidance on how to upgrade from Query Patroller and DB2 Governor
|
