data server as the target. This KM support the following Teradata optimizations:
Primary Indexes and Statistics Optimized Temporary Tables Management
IKM Teradata Slowly Changing Dimension
Integrates data in a Teradata target table used as a Type II Slowly Changing Dimension in your Data Warehouse. This IKM relies on the Slowly Changing Dimension metadata set on the target datastore to figure out which records should be inserted as new versions or updated as existing versions.
Because inserts and updates are done in bulk set-based processing, this IKM is optimized for large volumes of data.
Consider using this IKM if you plan to load your Teradata target table as a Type II Slowly Changing Dimension.
To use this IKM, the staging area must be on the same data server as the target and the appropriate Slowly Changing Dimension metadata needs to be set on the target datastore.
This KM support the following Teradata optimizations: Primary Indexes and Statistics Optimized Temporary Tables Management
This KM also includes a COMPATIBLE option. This option corresponds to the Teradata engine major version number. If this version is 12 or above, then a MERGE statement will be used instead of the standard INSERT then UPDATE statements to merge the incoming data flow into the target table.
IKM Teradata to File (TTU)
Integrates data in a target file from a Teradata staging area in replace mode. This IKM requires the staging area to be on Teradata. It uses the native Teradata utilities to export the data to the target file.
Consider using this IKM if you plan to transform and export data to a target file from your Teradata server.
To use this IKM, the staging area must be different from the target. It should be set to a Teradata location.
This KM support the following Teradata optimizations: Support for Teradata Utilities
LKM File to Teradata (TTU)
Loads data from a File to a Teradata staging area database using the Teradata bulk utilities.
Because this method uses the native Teradata utilities to load the file in the staging area, it is more efficient than the standard “LKM File to SQL” when dealing with large volumes of data.
Knowledge Modules Reference Guide