The database that holds all the foreign server objects is TD_SERVER_DB.
- Copy foreign server object definitions from a source database to a target database by copying the entire TD_SERVER_DB database or by copying foreign server objects only.
Copy Option Description Entire TD_SERVER_DB Database All foreign server objects exist in database TD_SERVER_DB. You can copy the entire TD_SERVER_DB from one Teradata system to another Teradata system by specifying the database selection="included" attribute for database TD_SERVER_DB; no other attribute or properties are needed. <dmCreate> ... <database selection="included"> <name>TD_SERVER_DB </name> </database> ... </dmCreate>
Only Foreign Server Objects Definition You can copy certain foreign server objects by specifying the foreign_servers section in the job definition, and setting the selection="included" attribute for each of the foreign_server sections. There is no need to specify the database name; they should exist in TD_SERVER_DB only. The foreign_servers section should be after the views section in the job definition. <dmCreate> ... <foreign_servers> <foreign_server selection="included" > <name>MyServer</name> <map>sparsemap4amps1</map> <colocate>sparsecol2</colocate> </foreign_server> <foreign_server selection="included" > <name>MyServer2/name> <map>sparsemap4amps1</map> <colocate>sparsecol2</colocate> </foreign_server> </foreign_servers> ... </dmCreate>
Parameter Description colocate Co-location name, for sparse map only. map Map name. name Foreign server name. The MAPS feature parameters, map and colocate, are supported only in target systems using Teradata Database 16.10 or later.