You can create profiles to selectively control groups of distributed (DBAT) threads and connections, set thresholds for query acceleration (not covered in this article) or provide override properties to model your test subsystem to reflect the computing power of your production environment.
I searched for the manual which would explain how to write proper SQL. I never found it and the more I talked to people on which strategy I should follow, the less useful information I seemed to get. The same was true whenever I asked for general rules to decide which index was needed.
DB2 is particularly good at running complex query and analytical processing. Since all modern hardware contains multiple cores and CPUs, and many systems are composed of multiple machines, it is critical that DB2 run individual queries across all available computing resources.
One of the most common maintenance activities performed on a Db2 LUW database is running Runstats on tables and indexes. Accurate database statistics are vital for the Db2 Optimizer to produce the most optimal plans.
Whenever a performance problem arises, the database takes the blame, but is that really true? This article will provide a hand's on, step by step approach to determine where the problem is. "Guilty Until Proven Innocent"