With each new release, DB2 is getting smarter and smarter. However, DB2 is not yet clairvoyant enough to understand the intentions of all queries and turn them into optimal forms. What’s the bottom line? Do you need to worry about how you code? The answer is yes, but not as much as in the past.
We use Explain to find out the access path for a query. Jim Dee, from BMC shows you how you can compare the access path with previous versions of the query or package – comparing the estimated costs, and identifying those that have changed with a rebind.
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 -