Archives of the TeradataForum
Message Posted: Thu, 19 Jun 2003 @ 15:28:19 GMT
A better procedure might be to use TDQM to stop the query being run in the first place. You can set limits on query size and complexity and the query will be rejected or scheduled to run later. This relies on the explain giving a good estimate so your stats have to be good. It will however prevent you wasting CPU cycles on something you will later abort.
You could use priority scheduler to denigrate the performance of the query automatically then either kill it manually or contact the user to find out what they are up to.
|Copyright 2016 - All Rights Reserved|
|Last Modified: 27 Dec 2016|