Join our webinar to find out when it’s OK to say “never” to your DB2 Database maintenance.
June 3rd, 2015
at 1 pm EDST (New York)
at 19:00 CEST (Paris, Berlin, Madrid)
a 4-in-1 webinar:
We are presenting 4 new USE CASES :
1 - Never Used Objects:
Finally determine how many, which types, and—perhaps most importantly—what size are all of those “Never–Referred–To–Objects”?
2 - Never Executed Packages
Easily see which packages are clogging the catalog and directory. Get rid of the “dead wood” and watch the spring–cleaning effect cascade throughout.
3 - Never Executed SQL
Even when a package is still being actively used, what about any SQL statements within that are *not* being executed? Now you can find these as well. From this point on you should spend time only tuning the *running* SQL on your System!
4 - Never Change a Running System
This age old adage needs to be disregarded as far as DB2 V8 onwards is concerned. With Multi-row Fetch you can obtain over 50% CPU savings as well as large GETPAGE savings. Using WLX, it is simple to find the candidates to hone. Why not roll out a cost–saving project to introduce Multi–row fetch into the static programs that will save you the most?
This REAL 4 Use cases will show you how to use a DB2 performance warehouse
Comments