You can create and run jobs using the Data Mover DSA utility by setting the force_utility to DSA. When a force_utility is not specified, the Data Mover DSA utility is automatically selected when the Teradata Database is version 16.00 or later, provided that DSA is not a restricted case. See DSA Utility Setup before using the DSA utility.
When using DSA to copy data between systems, DSA preserves the block level compression. Data is only uncompressed on the target system if the target system has a different restore configuration (such as a different number of AMPs compared to the source system). If the target system has the same configuration as the source, the block level compression is preserved throughout the entire job. Since the data remains compressed in all scenarios when being transferred over the network, using DSA can result in significant performance improvement as compared to other copy methods when block level compression is used and the network is a limiting factor.
Rules and Restrictions
- The DSA utility is available for Teradata Database versions 14.10 or later. However, DSA support for Teradata Database versions earlier than 16.00 is limited.
- DSA does not support moving journals.
- DSA does not support copying partial tables or view data unless source staging is specified.
- Failed DSA jobs cannot be restarted using the restart command. Use clean up followed by start to rerun the job after resolving the failure issue.
- When copying a database where either the source or target database version is earlier than 16.20, DSA does not preserve objects that exist only on the target database .
- DSA does not support copying tables and databases when indexes are included in the job and the source or target database version is earlier than 16.20.
DSA Optional Parameters
| Parameter Name | Required | Description |
|---|---|---|
| target_group_name | No | A target group is composed of Media Servers used for copying data. It is recommended that either the source or target system acts as a Media Server. When either the source or target system acts as a Media Server, it means the database nodes on that system have BAR NCs installed, configured, and running. Corresponding default target groups are automatically created by the Data Mover DSA utility and are used to copy data in the Data Mover job. This parameter should only be used by advanced users who want to specify a designated target group instead of using the default group created by the Data Mover DSA utility. |
| parallel_builds | No | The number of index and fallback sub-tables that can be built concurrently during a restore. The maximum number of concurrent builds is 5, default is 5. |
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<dmCreate xmlns="http://schemas.teradata.com/dataMover/v2009"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance
xsi:schemaLocation="http://schemas.teradata.com/dataMover/v2009/DataMover.xsd">
<source_tdpid>sourceSys</source_tdpid>
<source_user>source_user</source_user>
<source_password>source_password</source_password>
<target_tdpid>targetSyc</target_tdpid>
<target_user>target_user</target_user>
<target_password>target_password</target_password>
<data_streams>1</data_streams>
<source_sessions>1</source_sessions>
<target_sessions>1</target_sessions>
<freeze_job_steps>FALSE</freeze_job_steps>
<force_utility>DSA</force_utility>
<log_level>99</log_level>
<dsa_options>
<target_group_name>my_target_group</target_group_name>
<parallel_builds>1</parallel_builds>
</dsa_options>
<database selection="unselected">
<name>db1</name>
<table selection="included">
<name>tb1</name>
</table>
</database>
</dmCreate>