Loading Data from Teradata Loading Data to Teradata

11-8 Oracle® Fusion Middleware Connectivity and Knowledge Modules Guide for Oracle Data Integrator

11.7.2 Integrating Data in Teradata

Oracle Data Integrator provides Knowledge Modules that implement optimized data integration strategies for Teradata. These optimized Teradata KMs are listed in Table 11–4 . In addition to these KMs, you can also use the Generic SQL KMs. The IKM choice in the Interface Flow tab determines the performances and possibilities for integrating. SQL LKM SQL to Teradata TTU Loads data from a SQL compliant source database to a Teradata staging area database using a native Teradata bulk utility. This LKM can unload the source data in a file or Named Pipe and then call the specified Teradata utility to populate the staging table from this filepipe. Using named pipes avoids landing the data in a file. This LKM is recommended for very large volumes. Consider using this IKM when: ■ The source data located on a SQL compliant database is large ■ You dont want to stage your data between the source and the target ■ Your staging area is a Teradata database. This KM support the following Teradata optimizations: ■ Support for Teradata Utilities ■ Support for Named Pipes ■ Optimized Temporary Tables Management Table 11–4 KMs for integrating data to Teradata KM Notes IKM Teradata Control Append Integrates data in a Teradata target table in replaceappend 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 replace 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 Table 11–3 Cont. KMs for loading data to Teradata Source or Staging Area Technology KM Notes Teradata 11-9 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 guess which 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 data server as the target. This KM support the following Teradata optimizations: ■ Primary Indexes and Statistics ■ Optimized Temporary Tables Management IKM Teradata Multi Statement Integrates data in Teradata database target table using multi statement requests, managed in one SQL transaction 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. Table 11–4 Cont. KMs for integrating data to Teradata KM Notes