Archives of the TeradataForum
Message Posted: Mon, 17 Jan 2005 @ 15:09:58 GMT
| Subj: | | Re: FastLoad VS MLoad |
| |
| From: | | Michael Larkins |
You might look at the time taken in the Acquisition Phases for both Fastload and MLoad. MLoad is very robust in its capabilities to do INS,
UPD and DEL operations on multiple tables from multiple files. Where Fastload is one table with one INS using one file (much simplier recovery,
if needed).
Mload adds 5 columns to each input record to facilitate recovery: record sequence #, file #, DML #, SQL# and one other that I am not
remembering off the top of my head. Regardless, these values are tracked, recorded and sent with the data into the worktable(s). It also takes
time to look for and eliminate any data in FILLER fields. Hence, the time spent outside of Teradata on the host computer (i.e. mainframe or
whatever) increases with Mload compared to Fastload. Then, if you are doing a lot of conversions from one data type to another, this can also
drive up the time it takes to complete.
So, depending on the power of your particular host computer is going to dramatically impact the amount of time that takes Mload to finish,
moreso than Fastload.
Hope this gives you a bit more insight into the time difference that you are seeing between the two different utilities.
Michael Larkins
Certified Teradata Master
Certified Teradata SQL Instructor
| 
