Which of the following property is true about FAST LOAD.
-
No more than 1 data type conversion is allowed per column during the Fastload
-
If an AMP is down FL cannot be restarted untill that AMP is back online
-
only load 1 empty table with one fast load job
-
Fast load assembles data in 64K blocks and then loads it using mutltiple sessions
-
Fast load supports triggers.
Fast Load has specific constraints: it permits at most one data type conversion per column for performance, requires all AMPs to be online for restartability, and loads exactly one empty target table per job. It does not support triggers during load operations.
Teradata FastLoad has several well-known constraints: it allows at most one implicit data type conversion per column, it cannot be restarted from a checkpoint while any AMP involved is down (it must wait for the AMP to come back online), and a single FastLoad job can only load into one empty table at a time. It does not support triggers on the target table (triggers are disabled/ignored during FastLoad), and its data-blocking mechanism isn't accurately described as fixed 64K blocks over multiple sessions — that description doesn't match how FastLoad actually moves data.