Why MultiLoad Utility supports only Non Unique Secondary
Index(NUSI) in the Target Table ?
Answer Posted / satya
whenever we define a SI an SI subtable is created in each
AMP.For USI they go for a hash distribution, and hence the
actual data row pointed by the USI subtable rows in one AMP
may not be in the same AMP as the subtable..so the AMPs
have to communicate, which is not supported by Multiload.
For NUSI the subtable will store references of only those
actual data rows who exist in the same AMP as the
subtable..they all point to the data in their own
AMP..hence AMPs dont need to communicate here.
Thus the AMPs work in parallal with NUSI and hence Mload
supports that.
| Is This Answer Correct ? | 6 Yes | 1 No |
Post New Answer View All Answers
Name the five phases that come under MultiLoad Utility.
What is meant by a node?
How will you solve the problem that occurs during update?
What are the things to be considered while creating secondary index?
How do you create tables? Exact syntax, and create profiles, users in teradata?
How can bottlenecks be identified?
How is MLOAD Teradata Server restarted after execution?
In general, how do you optimze any sql in teradata?
Can we collect statistics on table level?
Did you write stored procedures in teradata?
Hi Friends, Please send me Teradata Materials for certifications Thanks in advance !!
Can any one explain me the difference between BTEQ and MLOAD,TUMP. All canbe used for same purpose but still differnt methods. why ?
What is the purpose of joins in teradata?
Give the sizes of SMALLINT, BYTEINT and INTEGER.
how do you manage the production space. what are the proactive methods you can take ?