Copy SQL Stored Procedures | Teradata Data Mover - About Copying SQL Stored Procedures - Teradata Data Mover

Data Mover copies SQL stored procedures as follows:

• Data Mover retrieves the SQL stored procedure creation DDL by executing a show procedure dbname.spname SQL statement.
• Data Mover does not parse a create procedure DDL; it executes the exact same DDL on the target system. It does not relocate or rename stored procedure objects.
• If the procedure name in the procedure definition is not fully qualified, the procedure is created in the database having the same name as the source procedure database.
• If the table names in the procedure definition are not fully qualified, those tables must exist in the database having the same name as the source procedure database to avoid an error.
• If the object being copied does not exist on the target database, it is created on the target database. If the object does exist on the target database, the object is overwritten – unless the overwrite_existing_objects property is set to false. In that case, a create time error is generated.
• If a procedure is part of a full database copy, the procedure is copied with the database using DSA. It is not copied separately.

When copying a SQL stored procedure, the underlying table for the procedure must already exist on the target system, or be copied with the job. Depending on the stored procedure creation SQL, a JDBC error may occur when creating a stored procedure without the underlying table.