Home Page for the TeradataForum
 

Archives of the TeradataForum

Message Posted: Mon, 20 Jun 2005 @ 12:56:49 GMT


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


Subj:   Monitoring Priority Scheduler using Heart-beat queries in every Performance Group
 
From:   Anomy Anom

<-- Anonymously Posted: Monday, June 20, 2005 08:52 -->

We are in the process of modifying Priority Scheduler by adding 3 new Resource Partitions and 7 new Performance Groups, in addition to the 4 Performance Groups already in in Default.

Some want to run a "heart-beat" query in each of the 11 Performance Groups every 15 to 30 minutes or so around the clock.

This would produce a lot of data over time. What useful information would this produce? How would the results be analyzed if you did not know the number, nature and in what Performance Group other queries were running.

Would one hear-beat query running in the same Performance Group all the day be sufficient?

Is there a better approach?

Someone has suggested that a presentation at Partners last Fall suggested this multi-heart-beat query approach. If so, do you have any further information on the rationale behind it/ analyses to be done/ etc.


Thanks very much



     
  <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