Working With Staging Databases - Teradata Data Mover

Teradata Data Mover User Guide

Product
Teradata Data Mover
Release Number
16.10
Published
June 2017
Language
English (United States)
Last Update
2018-03-29
dita:mapPath
kmo1482331935137.ditamap
dita:ditavalPath
ft:empty
dita:id
B035-4101
lifecycle
previous
Product Category
Analytical Ecosystem
Work with staging databases by specifying staging at the following levels:
  • Database and table levels
  • Secondary staging database
  • System level
  • Job level
  • Database level
  • Object level
Target staging tables are created as NOPI tables unless TPTAPI_UPDATE is being used to load data to the staging table. TPTAPI_UPDATE does not support loading to a NOPI staging table. In this case, the target staging table is created with the same Primary Index as the source table. Source staging tables for a table object are created using the original source table ddl. Source staging tables for a view object are created the same way as the target staging table.
Specified staging databases are only used when the job needs to create temporary objects. The following table lists when a staging database is used, based on the force utility selected.
Force Utility When Target Staging Database is Used
Aster Target table exists and is not empty.
ARC Table is an RI child table on the source and does not exist on target system.
Table is an RI table that exists on the target database and has either a child or parent on target database.
Table has a trigger with a before action.
Job is a PPI partial copy and source staging is not used.
Job is a partial copy, source staging is used, and the target table is not empty.
Job is a partial copy, source staging is used, data is being copied with a view, and target name and target owner name is not specified.
Job moves column partition table with a primary AMP index to a non-empty target table.
Hadoop/T2H Object exists on the target database.
Job is a partial table copy.
T2T Target table exists and is not empty.
Target table is an RI parent.
Target table is an RI child.
Target table has indices.
Table is a temporal table.
Target table has secondary indices.
Job contains a trigger with action time before.
Target table has a trigger.
Job is copying view data to target view.
TPT Target table is not empty and is not performing an upsert.
Target table is an RI child and is not performing an upsert.
Target table has indices and not performing an upsert.
Table is a temporal table and is performing an upsert.
Target table has secondary indices and is not performing an upsert.
Job contains a trigger with action time before and is not performing an upsert.
Target table contains a trigger and is not performing an upsert.
Job is copying view data to target view.