 |
 |
Archives of the TeradataForum
Message Posted: Thu, 19 Jun 2003 @ 09:19:19 GMT
| Subj: | | Re: Aborting the transaction |
| |
| From: | | Charles, Alan |
You don't actually need PS to automatically lower the priority or abort a job - providing you have access to a TM that has Alerts
installed then this will do fine. I have found that setting limits for CPU and Amp I/O, and then automatically lowering the priority once
these limits have been breached to be highly beneficial in terms of smoothing the machine performance overall. You can exclude your live
jobs etc. via the 'exclusions' option, and you can even use 'Delta CPU' (if you're not in client/server mode) which will capture the likes
of run-away product joins very quickly - although you have to be careful to get your limit correct for this.
I tend to think that lowering the priority is a much safer option than aborting. There's always going to be situations where a job
suddenly takes a lot longer to run than expected. If it's a run-away query then lowering the priority will 'contain' the query to a smaller
percentage of the machine, allowing other jobs to be far less affected. If you have PS then you have greater granularity to be able to
automatically put a problem job out of harms way until it can be manually investigated.
Rgds,
Alan.
| |
