Db2 for z/OS SQL performance
Quality and efficiency are the main concerns for application developers. This also applies to the aspects of data access. After following this course, participants will be able to understand how the Db2 optimizer is able to optimally implement SQL queries, and they will be able to apply techniques to further optimize those SQL queries.
Query optimization and a good concurrency are emphasized. Also discussed are some aspects of logical and physical design, and the statistical information in the Db2 catalog used by the optimizer.
During the practical sessions the participants will have ample opportunity to practise all the discussed topics.
Schedule
| date | dur. | lang. | location | price | |
| 16 Dec | 3 | web based | 1875 EUR (excl. VAT) | ||
| 16 Dec | 3 | Leuven | 1875 EUR (excl. VAT) | ||
| SESSION INFO AND ENROLMENT | |||||
Intended for
Application developers, analysts and database administrators. Also anyone responsible for the optimization of ad-hoc queries, for example in an infocenter environment, or the queries used in the context of a Data Warehouse.
Background
Knowledge of Db2 (see Db2 for z/OS fundamentals course) and of SQL (courses SQL and relational databases fundamentals and SQL workshop).
Main topics
- Strategy: steps, actions and required information
- Logical design and physical structure: normalization and denormalization • optimal implementation of table spaces, indexes and tables
- The catalog: content • significance and use of the information • update by means of RUNSTATS or SQL • simulation of the production environment in a test environment • types of statistics information, runstats profiles, and optimizer feedback
- The Db2 access paths: tablespace scan • matching and non-matching index use • index-only access • list prefetch • direct access via RowID • hash access
- Relation between the SQL query and the access paths: stage-1 versus stage-2 • multiple index use • correlated versus non-correlated subqueries • the join methods • influence of the clauses ORDER BY, OPTIMIZE FOR, and FETCH FIRST • views and CTEs • materialisation (work files)
- The EXPLAIN function: exercises in reading and interpreting the access path descriptions, both for static SQL as well as through the Dynamic Statement Cache (DSC), with and without Visual Explain
- Query optimization: what do we know about the optimizer? • how do we use this information? • how to transform a stage-2 predicate into a stage-1 indexable predicate? • which filter factors are assumed by the optimizer? • are these realistic? • how to choose the optimal alternative for joins, correlated/non-correlated subqueries? • how do we know which index is the optimal one? • how do we influence the optimizer's decision? • case studies
- Use of one or more of the explain tables in the performance investigation: PLAN_TABLE, DSN_STATEMNT_TABLE, DSN_DETCOST_TABLE, DSN_FILTER_TABLE, and DSN_PREDICAT_TABLE
- Use of "hints" (new style) to influence the Db2 optimizer • predicate selectivity
- Use of the "virtual index" possibilities for carrying out a "what if" analysis
- Concurrency: choosing the application structure and the right Db2 parameters, lock levels and locking strategy
Training method
Lecturing with practical exercises.
Duration
3 days.
Course leader
Peter Vanroose.
Also interesting
Enrollees for this training also took the following courses:
| SESSION INFO AND ENROLMENT |