When dealing with a database, it is important to understand the “DB2 catalog” concept. The catalog is a set of DB2 tables that store the DB2 system state. Almost every action that takes place in DB2 is reflected in a change to one or more catalog tables.
Ever hear the saying that the most efficient SQL statement is the one that is never executed? Well, it’s true.
We hope that you’ve enjoyed this month’s articles on DB2 performance on z/OS.
We talked about the new performance possibilities in DB2 11, about performance hints and tips for framework development, about explaining tuning to C-level and about efficient ways of replication.
The second entry of this month’s theme, DB2 for z/OS performance, is a video by Thomas Baumann covering “Tuning Explained to C-level”. Take the time to watch this great video by one of IDUG’s Hall of Famers. Because, as important as tuning your system, is explaining what you did to your management.
Rodney Krick has made available an analyzer for the DB2 JCC Trace on the IDUG Codeplace here -
He has written a tutorial on how to use it, which we are delighted to share with the IDUG Community -