Home Page for the TeradataForum
 

Archives of the TeradataForum

Message Posted: Tue, 11 Oct 2005 @ 15:45:23 GMT


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


Subj:   Re: Redestributing large tables instead of replicating a small table
 
From:   Howard Bradley

Er... not sure what you mean Michael, the example I quoted is the classic code to description lookup, so, only the code column exists on the large Sales table for example, (say store_id) , the query wants to find sales by store name rather than store id, so, the best performance I have found is to aggregate to store_id level from the large sales table first and then join this much smaller result set to the store lookup table to get the store name. I assume I haven't been producing the wrong results for the last 10 years but you never know :-)

So, my original question still stands, can the optimiser detect this sort of query and mimic this processing and if so in which version does it appear and how do I take advantage of it ?



     
  <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: 15 Jun 2023