On Wed, 6 Aug 2014 10:30:19 +1000, Wayne Bickerdike wrote:

>Bracket the potential dates in the SELECT and eliminate the ones you don't
>want using DFSORT in a later step. So if you are using CURRENT_DATE in the
>SELECT use >= CURRENT_DATE for the situation where the job clicks over to
>next date. 125 million rows is not a lot for DFSORT to filter later.

Say what !!!!
That's the (ex ?) DBA in you talking Wayne. As if we don't have enough trouble 
in the world from DBAs selecting everything, sorting it, throwing it away then 
doing it all again - when they only need a (smal) subset of the data.
Aggghhh - go read Radoslaws' "Anothe(r) SORT question" thread again.

DB2 is a pig as far as overall system management is concerned - just like every 
other database system. "Give me everything (page-fixed), the rest of the users 
can go slowly stew in hell".

Shane ...

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to