 |
 |
Archives of the TeradataForum
Message Posted: Tue, 07 Mar 2006 @ 10:33:11 GMT
| Subj: | | Re: Performance of Fastload vs Multiload |
| |
| From: | | Dieter Noeth |
Ole Dunweber wrote:
| | At the end of phase 1, this "table" is UNSORTED - I guess it's just a bunch of data blocks inaccessible by SQL. | |
| | Where as the MLOAD worktable is a "normal" sorted table. | |
IMHO Phase 3 of a MLoad (Aquisition) is equivalent to a FastLoad into the worktable, it probably *is* a FastLoad, but only the developers know
that :-)
So everything within the Application phase is overhead compared to FastLoad (In fact even loading the worktable should be more work because of
the extra columns, match tag etc.)
Dieter
| |
