Data Mover supports copying those foreign server objects definitions from one Teradata system to another Teradata system.
All the foreign server objects are kept in the database TD_SERVER_DB. This database exists in Teradata Database 15.0 or later.
For information about how to create, update, drop, or use foreign server objects, refer to the Teradata Database documentation.
Requirements and Restrictions
- Creating and copying foreign server objects requires that the respective foreign server packages are installed and configured properly on the Teradata Database system. If you need assistance, contact the Global Technical Support Center at https://support.teradata.com.
- The Data Mover job user must be granted permission for foreign server objects; otherwise, the job fails.
- Data Mover retrieves the foreign objects DDL by executing the SHOW FOREIGN foreign_server_name SQL statement.
- The Teradata Database system user must be granted permission for foreign server objects; otherwise, the job fails.
- Both source and target systems must be Teradata systems at version 15.0 or later.
- Data Mover does not parse a foreign server object DDL; the exact same DDL is run on the target system.
- Copy foreign server object definitions only.
- Relocation is not supported; all foreign server objects must be in database TD_SERVER_DB.
- Partial copy is not supported.
- Row count validation is not supported.
- Compare DDL is not supported.
- Using staging tables and staging databases is not supported when moving foreign server object definitions.
- Foreign server object definitions can be copied using DSA, TPT, or JDBC.
- 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.