Home Page for the TeradataForum
 

Archives of the TeradataForum

Message Posted: Thu, 18 Dec 2003 @ 19:49:25 GMT


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


Subj:   Re: Physical Implimenation Issue
 
From:   Hassinger, Bill

Make sure you table _y is a MULTISET table so dup check is not being done during the maintenance.

***********

I have a table called Table_x and it has 20 columns and 10 K rows. I have another table called Table_y and it has 7 columns and 10 Million rows. The Unique Primary index on Table_x is its column-1 and that is exactly the column-1 in Table-y. The unique primary Index of Table-y is its columns 1, 2, and 3. Columns 2,3 of Table-y not exists in Table-x.

In this case, the Load performance is the best and the skew factor in Table-y is 0.

The query performance is the worst in the above case when I join Table-x to Table-y. Then I changed the Unique Primary Index of Table-y to just Primary Index on column-1.

The query performance is the best in this case, but the load performance affected severely. The skew factor now is 22.

Could anybody who did this type of installation give me a better solution?


Many thanks in advance

Ganga Palakattil



     
  <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