Archives of the TeradataForum
Message Posted: Wed, 28 Oct 2015 @ 20:14:14 GMT
UNIQUE INDEXES will require the duplicate checks regardless of MULTISET or SET. SET will allow 1 and only 1 "SET" of the data - no duplicate rows.
MULTISET will allow MULTIPLE SETS of DATA, however you are negating that option by using UNIQUE INDEX structures.
Multiloads and such are faster with NUPI and MULTISET as it indeed does not check for duplicate row instances. FASTLOAD utility automatically eliminates duplicate rows regardless of MULTISET or SET options.
IF you want the most efficient of the options - a NO PRIMARY INDEX table is the fastest (has to be inherently MULTISET) as it will not check existence for duplicates and randomly places data on the AMPS - potentially eliminating HASH COLLISIONS. Caveat here as lumpy data from a skewed source table with a straight insert to NOPI table can still generate LUMPY results as the data never leaves the original AMP.
Kyle Prescott>Kyle Prescott
|Copyright 2016 - All Rights Reserved|
|Last Modified: 23 Jun 2019|