Never say never?

Recordings from June 3rd, 2015

Duration: 20 Minutes in 4 parts

Webinar presented by SEGUS & SOFTWARE ENGINEERING

Join our webinar to 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

Introduction (3 min)       Presentation

 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?

 

Introduction

 

1- Never Used Objects

 

2- Never Executed Packages

 

3- Never Executed SQL

 

4- Never  Change a Running System