This section provides an overview of the typical Teradata SET emulation process. It is assumed that SystemFE.Opt_Cost_Table and SystemFE.Opt_RAS_Table exist on the target system.
The process is as follows:
1 Connect to a Teradata Database using a Teradata Open Database Connectivity (ODBC) driver or Teradata Call‑Level Interface, Version 2 (CLIv2).
2 Create a target system profile that defines the databases, tables, views, macros, and related environmental parameters or RAS to be captured and loaded onto the test system.
3 Perform an export operation from the target system to collect Optimizer cost parameters; RAS; and any necessary object definitions, statistics, and test queries from the target system. Then, place this emulation information on the system disk as data files that the test system can import.
4 If the target and test systems are not connected to the same network, perform a pack operation to combine all the data files into one file. (Pack files also can be compressed using any standard compression method.) Transfer the files to the test system.
5 Perform an import operation to create the objects, emulate the statistics, and import the data into SystemFE.Opt_Cost_Table and SystemFE.Opt_RAS_Table on the test system.
6 Set emulation on the test system, and use the data to test and resolve any problems or discrepancies.
The Teradata SET Architecture illustration below shows The relationship between Teradata SET, the ODBC and CLIv2 interfaces, target systems, and test systems.Figure 1: Teradata SET Architecture