Copy Views, Macros, and Stored Procedures Using DSA | Teradata Data Mover - About Copying Views, Macros, and Stored Procedures Using DSA - 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

In Data Mover, you can copy views, macros, and stored procedures definition, and create those objects on the target system using DSA. It does not required the underlying dependent object of the copied objects in the target system. You can also use SQL instead of DSA, but it requires the underlying dependent object of the copied objects in the target system.

To copy these objects using DSA, specify the force_utility element value as dsa in the job. For example:
<dmCreate> 
...
   <force_utility>dsa</force_utility>
...
   <views>
        <view selection="included">
            <name>view1</name>
            <database>database1</database>
        </view>
   </views>
   <macros>
	<macro selection="included"> 
		<name>macro1</name>  
		<database>database1</database> 
	</macro> 
   </macros>
   <stored_procedures>
        <stored_procedure selection="included">
            <name>storedprocedure1</name>
            <database>database1</database>
        </stored_procedure>
   </stored_procedures>
...
</dmCreate>

If you do not specify the force_utility element value, then it uses SQL for copying objects.