Hello,

Regarding the workload management features described at
http://publib.boulder.ibm.com/infoce...w/v9r7/nav/3_4 :
Are none, some, or all of the workload management features included in
DB2 Enterprise Edition?

--
Troels

"Troels Arvin" <troels (AT) arvin (DOT) dk> wrote

It is an extra cost add-on, part of the Performance Optimization Feature
Pack for DB2 ESE (only). Be careful, because the licensing for some features
is not enforced yet (not sure about this one, but Storage Optimization
feature licensing is not hard enforced in some releases).

On Oct 14, 5:12*am, "Mark A" <no... (AT) nowhere (DOT) com> wrote:
Hello Troels,

You might want to check the new Advanced ESE. The price is only a 10%
premium, but you get compression, workload management, LBAC,
Performance Manager and some other things included. I think it's
actually cheaper than it was to buy just one option pack before...
It's good to see easier access to these features for everyone.

--
Frederik

(Thanks to Mark and Frederik)

Does anyone here have experience with the DB2 Workload Manager? I
expect that it provides a way to be able to give better guarantees
about batch jobs, such that ad-hoc queries cannot lock resources need
by a batch-job?

If you have experience: Does it work well? Is it worth the extra cost,
in your opinion, or is it better to solve it's goals with other means?

--
Troels

On Oct 14, 11:53*am, Troels Arvin <tro... (AT) arvin (DOT) dk> wrote:
This is a bit besides the question, but my guess is that they put it
all together in a pack just becáuse there weren't too many people
getting experience with it :-) Probably the same reason they started
including PureXML for free, too.

Since you mention locking, my understanding is that it won't help
there directly. You will be able to make either job run faster than
the other so it's finished earlier, you can limit the 'size' of the ad
hoc queries or the number that run concurrently, but there's no way to
let a higher priority query take over the lock from a lower one, for
example. The Currently Commited isolation level from 9.7 will probably
help more in that case, are you using this?

Like Mark said, it's probably not enforced. Give it a try in a test
environment and let us know the results.

--
Frederik Engelen

"Troels Arvin" <troels (AT) arvin (DOT) dk> wrote

I am not an expert in this feature, but I know you can provide CPU priority
on application connections based on things like the application name,
userid, etc. I don't think it affects database locking directly.