In case of ideal senario for FastLoad why do we consider Fastload instead of Multiload where both are Bulkload(64kb).
Correct me if I am wrong, the populare answer I got is is Fast Load use 2 phaze where Multiload consists of 5, which I really doubt.
Cause the phase of Multiload -
- Initialization of Layout
- Clean off
all are this are applicable for even fast load aren't they?
Fastload has two phases: acquisition phase and application phase. mload has 5 phases(Note: however there is no acquisition phase for mload delete).
mload phases: Preliminary,DML Transaction,Acquisition,Application,Cleanup.
The name itself is fast load.
In your first line "In case of ideal senario for FastLoad why do we consider Fastload instead of Multiload" You know that the scenario is ideal for fastload, then what made you think about MLOAD for this scenario?
Not sure that above answers the orig question.
I guess the number of phases are irrelevant. Usually total time to get things done is what matters.
But both utilites come with limitations.
Fastload can only load into empty tables.
Multiload can also load data into populated tables but support only NUSIs on the table.
Multiload loads the data into work tables. Prepares the data block wise and apply whole block changes.
These days Fastload with NOPI and merge is comparable fast but will have less limitations on indices and can also has more benefits. Some customer are using this as default szenario and I guess number is growthing.
Considering "ideal senario" which means empyt table. The resource and time difference is not very big. Automated NUSI maintenance is easier with MLOAD as it does not require separate steps. Also you might want to deal with less utilities as they all have different syntax and debuging needs. So if you use MLOAD for some cases it might be worth to run all loads with MLOAD only.
Sorry if my question is not clear, In fact you wrote that the scenario is ideal for Fastload, thats why I deduced you know much about these utilities.
Ulrich has explained what I was thinking. Hope you got answered.
I feel that at the end of the day, it depends on what suit the end requirements well. But just a comparison of fload and mload for empty tables and no indices, fload is a bit faster(though both are close), since it does not log extra information compared to mload. This is my understanding.
if i ahve a data like
total 100 records
1. 50 records complete row duplicated.
2. 10 records data type is different .
3. 40 records unique and good data.
my question is
Q : using fastload and multiload what are the error tables and log information ?