named pipes avoids landing the data in a file. This IKM is recommended for very large volumes.
Depending on the utility you choose, you'll have the ability to integrate the data in either replace or incremental update mode.
Consider using this IKM when:
You plan to load your target table with few transformations on the source
All your source tables are on the same data server (used as the staging area)
You don't want to stage your data between the source and the target
To use this IKM, you have to set the staging area to the source data server's schema.
This KM support the following Teradata optimizations: Primary Indexes and Statistics Support for Teradata Utilities Support for Named Pipes Optimized Temporary Tables Management
IKM Teradata Control Append
Integrates data in a Teradata target table in replace/append mode. When flow data needs to be checked using a CKM, this IKM creates a temporary staging table before invoking the CKM.
Consider using this IKM if you plan to load your Teradata target table in append mode, with or without data integrity check.
To use this IKM, the staging area must be on the same data server as the target Teradata table.
This KM support the following Teradata optimizations: Primary Indexes and Statistics Optimized Temporary Tables Management
IKM Teradata Incremental Update
Integrates data in a Teradata target table in incremental update mode. This IKM creates a temporary staging table to stage the data flow. It then compares its content to the target table to calculatewhich records should be inserted and which others should be updated. It also allows performing data integrity check by invoking the CKM.
Inserts and updates are done in bulk set-based processing to maximize performance. Therefore, this IKM is optimized for large volumes of data.
Consider using this IKM if you plan to load your Teradata target table to insert missing records and to update existing ones.
To use this IKM, the staging area must be on the same
Knowledge Modules Reference Guide