 |
 |
Archives of the TeradataForum
Message Posted: Tue, 19 Feb 2013 @ 15:23:35 GMT
Subj: | | Tables: How small is small for TD to dynamically |
|
From: | | Attila_Finta |
I have a question regarding PI definition for small tables. Teradata replicates small tables across all AMPs (when joined to another table
having a different PI). Therefore we have been recommending that small tables should have a Unique PI that is the same as the PK (to maximize
even distribution). For larger tables I believe we must also consider frequent access points and join paths. Do you have any guidance re: "how
small is small"? How small is small enough for TD to replicate the table? 1 MB? 10 MB?
Thanks.
Attila Finta
| |