Home Page for the TeradataForum

Archives of the TeradataForum

Message Posted: Tue, 18 Jan 2005 @ 06:19:17 GMT

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

Subj:   Re: FastLoad VS MLoad
From:   Narayan Murthy

If your data were to be badly skewed(i.e. considering NUPI) and you have a SET table to be loaded then MLOAD takes a longer time - because it checks every row to be inserted for duplicates. Added to this error logging (logging the duplicate row to the error table) would again take some cosiderable time. You could avoid this if you were to have a MULTISET table as the target table to be loaded.

Fastload however does not allow duplicate rows even though the table is MULTISET (it handles the elimination internally).


  <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