X hits on this document

388 views

0 shares

1 downloads

0 comments

129 / 131

Load

Reverse- Engineer

Consider using this LKM if your source is a large flat file and your staging area is a Teradata database.

This KM support the following Teradata optimizations: Statistics Optimized Temporary Tables Management

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 file/pipe. 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 don't 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

RKM Teradata

Retrieves metadata from the Teradata database using the DBC system views. This RKM supports UNICODE columns.

Metadata includes tables, views, columns, Keys (primary indexes and secondary indexes) and Foreign Keys. Descriptive information (Column titles and short descriptions) are also reverse-engineered.

Note that Unique Indexes are reversed as follows:

The unique primary index is considered as a primary key.

The primary index is considered as a non unique index.

The Secondary unique primary index is considered as an alternate key

The Secondary non-unique primary index is considered as a non-unique index.

You can use this RKM to retrieve specific Teradata metadata that is not supported by the standard JDBC interface (such as primary indexes).

Knowledge Modules Reference Guide

129/131

Document info
Document views388
Page views391
Page last viewedWed Dec 07 20:29:50 UTC 2016
Pages131
Paragraphs3942
Words42855

Comments