Specifying a Secondary Target Staging Database

Teradata Data Mover User Guide

Analytical Ecosystem
Teradata Data Mover
User Guide

If you specify a staging database, the staging database by default contains the staging target table and any work tables, log tables, error tables, or macros that need to be created. You may want the staging target table to be created in a staging database that is separate from the staging database where the work tables, log tables, error tables, and macros are created.

You can specify a secondary staging database to hold only the staging target table by using the optional staging_database_for_table tag in the job creation XML file. If the value for the staging_database_for_table tag is specified, that database is used as the staging database for the staging target table. The staging_database tag is still used for specifying the general staging database in which the work tables, log tables, error tables, and macros are stored.

Similar to the staging_database tag, the staging_database_for_table tag can be applied either at the database level or at the table or view level. The value specified at the table or view level overwrites the value specified at the database level.

Data Mover supports using either the staging_database or target_staging_database tags to specify the target staging database, but not both at the same time.