Compare DDL when Moving Underlying Data from a View | Teradata Data Mover - About Comparing DDL When Moving Underlying Data From a View - Teradata Data Mover

Teradata® Data Mover User Guide - 20.01

Deployment
VantageCloud
VantageCore
Edition
Enterprise
IntelliFlex
Lake
VMware
Product
Teradata Data Mover
Release Number
20.01
Published
November 2023
Language
English (United States)
Last Update
2023-12-05
dita:mapPath
hlv1700545853003.ditamap
dita:ditavalPath
mpm1591127278842.ditaval
dita:id
don1467241476387
Product Category
Analytical Ecosystem
When moving data from a view using copyData="true" you can compare the view columns with the columns of the target table using the compare_ddl feature.
The compare_dll feature is not used to compare the definition of the source and target views. It is used to compare the columns of the source view with the columns of the target table.
When copying time series tables, compare_ddl also compares the primary time index which includes the following fields:
  • TSFlags
  • timeZero
  • TimeBucketUnit
  • TimeBucketValue
To copy time series tables to a non-time series table, set compare_ddl to false, otherwise the job fails.
In order to compare the source view columns with the target table columns, the compare_ddl element needs to be specified as true. This is optional with a default value of true.
<views>
	<view selection="included" copyData="true">
		<name>deptsals</name>
		<database>MyDb</database>
		<view_data_table>
			<target_table>TargetTable</target_table>
			<target_database>TargetDb</target_database>
		</view_data_table>

		<staging_database>
			<name>TargetDb_Staging</name>
		</staging_database>

		<compare_ddl>true</compare_ddl>
	</view>
</views>
When copying view data, the compare_ddl element is not considered if the target data table does not exist on the target system or if copying view data to target view.