Home Page for the TeradataForum

Archives of the TeradataForum

Message Posted: Wed, 04 Feb 2009 @ 23:07:04 GMT

  <Prev Next>   <<First <Prev Next> Last>>  

Subj:   Re: Automating priority for bad queries
From:   Woodrow, Steven

If you set their max spool at 500 GB, it will be self managing. If they go over, their queries will be terminated.

Allowing the max spool to terminate queries is a harsh, but very effective at stopping runaway queries from overconsuming. (Personally, I think this is underused!)

Otherwise, TASM does have the ability to create an exception on Spool, but I have never tried it. Theoretically, it should work.

TASM can also look for certain criteria within exceptions that identify bad queries. You can have exceptions on CPU Milliseconds per I/O (Product joins), CPU limits, Skew, etc. Once detected, you can page a DBA, abort the query, and/or other actions.

Teradata Manager Alerts can also be used to page you for certain criteria as well. CPU Skew, Number of I/Os, etc.

Steve Woodrow

Teradata Professional Services
Performance and Workload Management COE

  <Prev Next>   <<First <Prev Next> Last>>  
  Top Home Privacy Feedback  
Copyright for the TeradataForum (TDATA-L), Manta BlueSky    
Copyright 2016 - All Rights Reserved    
Last Modified: 27 Dec 2016