Database Client Encryption | Teradata Data Mover - About Database Client Encryption - Teradata Data Mover

Teradata® Data Mover User Guide

Product
Teradata Data Mover
Release Number
16.20
Published
November 2021
Language
English (United States)
Last Update
2021-11-04
dita:mapPath
wph1512683331242.ditamap
dita:ditavalPath
4101_UG_dm_1620.ditaval
dita:id
B035-4101
lifecycle
previous
Product Category
Analytical Ecosystem

You can encrypt data during a transfer. Data can be encrypted at the system, job, and object level by using either the system level property job.databaseClientEncryption, or the job and object level property db_client_encryption.

Client encryption behaves differently depending on the force_utility selected:
Utility Behavior
ARC or TPTAPI Data is encrypted during transfer.
QueryGrid, JDBC, or Hadoop Only the connection between the source and target system is encrypted, not the data.

Scope Levels and Priority Logic

The following table shows the objects included at each scope level, and the priority logic applied if you specify different values at the scope levels. If you set the database client encryption flag at more than one scope level, the smallest scope has the highest priority. For example, if you set job.databaseClientEncryption to true at the system level, but false at the job level, the data transfer for this is not encrypted.
Scope Level Objects Compared Priority
Object The specified table or view Highest
Job All tables and views in the job High
Daemon All tables and views processed by a specific daemon Low