 |
 |
Archives of the TeradataForum
Message Posted: Thu, 24 Apr 2003 @ 21:31:00 GMT
| Subj: | | Dealing with Hot Amping.. |
| |
| From: | | Frank C. Martinez IV |
Hello to all my Teradactyl friends,
Given that some hot amping is inevitable, as long as it doesn't last forever (ok, those of you in a perfect world, please close your
ears), is there a way to deal with the offending query short of killing it (uh, and the developer who a) doesn't like to look at Explains,
b) doesn't really want to know how Teradata works, c) thinks his physical design class in DB2/Oracle/Sybase/whatever makes him an expert on
databases)?
What I'd really like to do is put it on hold (yes, I know, it would still take up spool, but that would be the offending user's problem,
natch?) for a while and let other, nicer queries (the ones that know how to play with the other children) finish. Then let the ugly query
finish. Of course, if I just dropped the priority, the stupid hot amp would just go on LONGER (not a nice look). I'd like to let it stay
in stasis as far as processing is concerned, letting the VAmps (why do I always have visions of some Unix process lounging on top of a
piano?) do other work until the system quiesces.
Anyway, I figured while people were waiting for pigs to grow wings or Teradata to be on Linix, I'd ask another of my wild hare
questions.
"Arf!"
iv
| |
