A Data Mover job consists of the following:
- A user-provided definition of database objects that Data Mover copies from the source to the target, such as a copy of a table from the PROD1 Teradata Database system to the DEV1 Teradata Database system.
- A programmatically-generated plan of sequential and parallel tasks to optimize job execution, such as distributing job execution into tasks across several servers.
Create a job when you want to copy database objects. A job is useful for:
- Copying one or more tables from an existing Teradata Database system to a backup Teradata Database system, where data in both systems stays synchronized
- Copying data from a production Teradata Database system to a staging or test Teradata Database system
- Migrating data regularly in one direction from the original to a backup
When creating a job, you select source and target databases and specify the source database objects to copy. You can also refine the job definition to control performance, logging, and other factors.
Spaces in the user name for the source or target id causes the job to fail.
Spaces in the account name for the source or target account id causes the job to fail.