Home Page for the TeradataForum
 

Archives of the TeradataForum

Message Posted: Fri, 07 Dec 2012 @ 19:45:44 GMT


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


Subj:   Re: Creating Sequence Number In Table To Fix Amp Skew
 
From:   frank.c.martinez

Exactly! If both account and customer id distribute well, and you join frequently to the acct/cust table from the acct table, then using the acct id makes sense. If you join to the cust table, then that would be the better index. The list of business questions could suggest one or the other. If joins occur in one direction (acct to acct/cust), p'haps access in the other direction might be directly by a cust id value, which would suggest trying a secondary index. Or if there are business questions that require the cust to acct/cust join, p'haps a join index with the columns that cover those queries would be most appropriate. Having a logical model and knowing the top business questions will assist in this design.


iv



     
  <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: 23 Jun 2019