Description
Delivery:Online, classroom or onsite
Duration:5 days (40 hours)
Platform:Db2 for z/OS
Who it is for:Programmers and DBAs responsible for application performance on Db2 for z/OS.
Recommended background:Experience with SQL on Db2 for z/OS and with program preparation.
Who this course fits
- Teams with a batch process that no longer fits its window.
- DBAs being asked for a new index for every slow query.
- Programmers who have to justify the cost of a query before shipping it.
Course content
- Introduction to application performance and tuning
- Common causes of performance problems and how to detect them
- Performance analysis tools
- Components of local response time: random touches, sequential touches and fetch
- Estimating response time before running
- Locating the values in an accounting trace report
- Drawing and interpreting a bubble chart
- Towards better indexes: Db2 index structure and usage
- Evaluating the cost of creating or modifying an index
- Designing the best possible index for a query
Course agenda
- Day 1: introduction and common causes
- Day 2: analysis tools and local response time
- Day 3: accounting traces and bubble charts
- Day 4: index structure and usage
- Day 5: index design and the cost of creating them
Training with SIXE, IBM Business Partner
- Labs on a real z/OS and on the Db2 release you have installed, whether that is 12 or 13.
- Taught directly by IBM Champion instructors from the SIXE team.
- Credly badges available: credly.com/organizations/sixe/badges
- Flexible format — online, classroom or onsite — in closed groups, priced per attendee, in the language of your choice (ES / EN / FR).
Instructors specialised in IBM Db2 for z/OS
Engineers from the SIXE team who administer and tune Db2 for z/OS in production. Several recognised as IBM Champion.
Frequently asked questions
Do we work with real traces?
Yes. Reading an accounting trace report and knowing which number to look at is one of the core parts of the course.
Will more indexes not solve it?
Almost never, and the course teaches exactly how to weigh the cost: every new index is paid for in inserts, in utilities and in space. The index design unit is about picking the right one, not adding another.
What if the SQL itself is the problem?
Then the companion course is CV964G, which is specifically about SQL performance and tuning.
Group size and language?
Closed groups of four to ten people, in Spanish, English or French. We run it with fewer than four as well, though it usually pays to wait and fill the group.
Related courses
- CV964G — Db2 12 SQL performance and tuning (the SQL side, in detail)
- CV722G — Db2 13 application programming (the programming groundwork)
- CV871G — Db2 for z/OS utilities (if the window goes on utilities)
