Never say never?

 

Aufzeichnungen vom 3. Juni 2015

Dauer: 20 Minuten in 4 Teilen

Webinar präsentiert von SOFTWARE ENGINEERING (engl)

Find out when it’s OK to say “never” to your DB2 Database maintenance.

How to use a DB2 Performance warehouse for real world Use Cases

a 4-in-1 webinar

Einleitung           Präsentation

 1

Never
Used Objects
 

(5 min.) Finally determine how many, which types, and—perhaps most importantly—what size are all of those “Never–Referred–To–Objects”?
 2

Never
Executed Packages

(2 min.) 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

(2 min.) 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

(3 min.) 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?

 

Webinar Einleitung 

 

Never  Used Objects 

 

Never Executed Packages

 

Never Executed SQL


Never Change a Running System