Quantcast
Channel: Teradata Forums - All forums
Viewing all articles
Browse latest Browse all 27759

AMP - Storing the Record - response (4) by Adeel Chaudhry

$
0
0

In such a scenario .... one should think before choosing a PI.
 
It is not a bug of Teradata .... it just doesn't expect a PI to be a column which have only 2 unique values .... imagine a warehouse for some Telecom and putting PI on such combination would obviously doesn't make sense. Teradata is built for DHW .... where the data is dynamic, changing and growing and PIs are not made on such columns.
 
Selecting correct PI is also important to completely utilize the true parallel nature of Teradata. Which you are not going to use in such a case. Every query hitting the table will only be utilizing 2 AMPs .... and usually Teradata Nodes does have alot more AMPs.
 
To the friends, well its the way Teradata stores data .... and if it is given a false parameter to store data .... its our friend's bug .... :).
 
As a general rule, PI should be the column(s) which are selected on the basis of table's usage and provide best data distribution among 'ALL' AMPs with minimum skewness.
 
HTH!


Viewing all articles
Browse latest Browse all 27759

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>