Talk to a Training Advisor
Availability
Schedule available upon request within 24 hours.
|
Also known as: CF96N2GBGB
About this class Prevent application performance problems and improve the performance of existing applications. Who will the lesson benefit? DB2 specialists and experienced application developers What delegates will learn Learn to design better indexes - Learn to live with the optimizer (avoid pitfalls, help when necessary)
- Avoid locking problems
- Use Spike Report to find significant performance problems in an operational application
What prerequisites are required Familiarity with DB2 application programming. For developers: CF03U, CF12GB, and CF82GB, or equivalent experience. For database administrators: CF03U, CF12GB, and CF83U, or equivalent experience. - DB2 Family Fundamentals (CF03U)
- DB2 SQL Workshop (CF12GB)
- DB2 UDB for z/OS Application Programming Workshop (CF82GB)
Contents of this class Overview of application performance issues and performance management methods. Towards better indexes - From data model to database version 0
- Detecting inadequate indexing with VQUBE
- Three-star index: deriving the best possible index for a SELECT
- Estimating the cost of an index
- Restrictions and limitations
Towards better tables - Relationship 1:C, one or two tables?
- Clustering
- Denormalization
- Massive batch
- Problem no 1: random disk I/O
- Estimating and minimizing disk I/O time
- Manual and automatic parallelism
- Massive deletes Unpredictable transactions
- Unpredictable predicates
- Many criteria, few provided
- Star join
- Fat indexes vs summary tables
Worried about CPU time? - Worksheet for rough CPU time estimates
Learning to live with the optimizer - Predicting index matching and screening
- Indexable predicates
- Boolean Term predicates
- - REOPT(VARS) and the alternatives
- Join issues
- Subquery issues
- Union issues
Preventing long lock waits - Lock life cycle
- Hot pages, hot rows
- Recommendations
Tuning operational applications - Analyzing slow transactions with spike report
- Detecting inadequate indexing
- Detecting optimizer problems
- Detecting long lock waits
- Detecting tables which should be denormalized
Tomorrow - Computer-assisted index design
- Hardware
- Are your applications scalable?
|