To solve the problem finally, you will have some DB2 expert to
examine the SQLs that the remote users are sending. Because
very often the people "outside" send the SQL through end user tools,
they are not well trained and could do much better. This will cost some
money at the start, but in the long term it will save you lots of money.
I'm working in the SQL training business from time to time, and I saw
horrible SQLs which wasted machine time for hours, issued from remote.
Kind regards
Bernd
Am 02.03.2011 02:12, schrieb Ted MacNEIL:
We are having occasional performance issues that appear to be rooted in some
interactive research queries.>The words 'DB2 governor' have been mumbled, but
some think that the WLM would be a logical starting point.
Details?
I've found the worst thing you can do is use the Governor to cancel a query
before it's complete!
First, you've wasted the resouces that were already consumed.
Second, the user usually re-submits.
It's much better to extend to multiple periods.
It will cost less, in the long run, and the user (IE: the business -- can we
say where your paycheque comes from?) is better served.
-
Ted MacNEIL
eamacn...@yahoo.ca
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
