Home Page for the TeradataForum
 

Archives of the TeradataForum

Message Posted: Fri, 10 Sep 2004 @ 18:16:32 GMT


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


Subj:   Priority Scheduler - how to partition
 
From:   Kumaran Anantaraman

We are looking to use PS. We are facing a fundamental question : Should I define the partitions along the type of work (tactical, strategic, ad hoc etc), lets call this config A, or should they be aligned by the business units (supply chain, HR, sales etc) config B?

Carrie's orange book shows 3 templates with template 1 and 3 corresponding to the above 2 alternatives respectively. I would like hear pros and cons from users on the alternatives. Here is a start.

Config A - by type of work

Pros

* Supports to enterprise vision and the typical DW classification of work

* The number of types of work is very stable


Cons

* ??


Config B - by business units

Pros

* (assuming business units are charged back), reserves database resources to a business unit based on what they paid for

Cons

* The limit of 5 RPs poses restrictions on scalability of business units


Is it possible to get the best of both worlds by defining the RPs by business units and the 2nd level Performance groups by type of work?

I understand how we use PS depends on specific issues we are trying to address at our site. For now, lets keep it neutral and assume the discussion is for a typical Teradata installation that's growing steadily.


Kumaran Anantaraman



     
  <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