Home Page for the TeradataForum

Archives of the TeradataForum

Message Posted: Sat, 23 Feb 2002 @ 19:28:31 GMT

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

Subj:   Re: NUPI considerations
From:   Thomas F. Stanek


I think Jim Judge has the most effective solution. Creating a NUPI on col1, col2 makes the most sense if the vast majority of the accesses into your large table are with a join to the smaller table and the calendar table. The optimizer should do just what Jim described. In this scenario, the Multiset and UPI wouldn't be necessary, at least not to maintain uniqueness.

If most of your large table accesses don't require the calendar table and consistently join to the smaller table, then a NUPI of col1 would work best. In this scenario, I wouldn't' consider Multiset unless you think that the load performance is unacceptable.

Sorry if I lead you astray.

Thomas F. Stanek
TFS Consulting

  <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: 28 Jun 2020