Hi !
Here is the problem:
I have the stored proc. with SET PDQ PRIORITY HIGH; inside it;
when I'm run it everything is fine, and onstat -u gives me a lot of
thread with the same SID. that relates to that procedure
but when the procedure. finished its work onstat -u give's me the same
pictures
on threads ! (In 7.2x it always gives me exactly one).
Even when i'm run SET PDQ PRIORITY LOW; and run some query (I'm using
SQL Editor 3.0)
the onstat -u doesn't change. Does it mean that those processes that
are linked to PDQ workout
are idling and eats my server resources even after all PDQ HIGH
statements (PDQ is stated inside procedure,
so it has effect only inside that proc) is finished ?
BTW. Right now I can't say what TC I'm using -- onstat -V gives TC2,
while all release documents in
release dir states TC1 and systables gives TC1 too. Could some one told
me what TC I'm using ? And
is there any other way that scanning systables to see the right answer
in SQL ?
Sincerely, Alexander
-- All opinions are my own and not those of my employer. --
|
| Alexander V.Didytch Kyiv, Ukraine, unknown.thegreat@usa.net
|
--
The professor rapped on his desk and shouted: "Gentlemen, order!"
The entire class yelled: "BEER!!!"