DIAGNOSTIC DUMP COSTS
Purpose
Extracts optimizer cost information calculated by the Trusted Parallel Application (TPA) and DBS Control flag information from a target system, then writes the information to the following tables on that system:
Syntax
where:
|
Syntax element … |
Specifies … |
|
target_system_name |
the name of the target (production) system from which optimizer cost information is calculated by the TPA. For information on object naming, see SQL Fundamentals. target_system_name is not case sensitive and and can be up to 63 characters in length. target_system_name is used as the primary index for the following tables: The primary index for SystemFE.Opt_Cost_Table is a UPI. The primary index for SystemFE.Opt_DBSCtl_Table is a NUPI. |
|
‘comment’ |
an optional string literal description for the request. The default character string is the specification for target_system_name. comment can be no longer than 255 bytes in length. |
ANSI Compliance
DIAGNOSTIC DUMP COSTS is a Teradata extension to the ANSI SQL:2011 standard.
Required Privileges
You must have the INSERT privilege on the following tables to dump costs:
Target Level Emulation and DIAGNOSTIC DUMP COSTS
DIAGNOSTIC DUMP COSTS does not require Target Level Emulation to be enabled in order to extract target system environmental cost data.
Session Mode Restrictions
You cannot perform DIAGNOSTIC DUMP COSTS in ANSI session mode or within explicit transaction boundaries in Teradata session mode.
Example
Dump the system environmental cost values for the optimizer on the current system to SystemFE.Opt_Cost_Table and the DBS Control flags to SystemFE.Opt_DBSCtl_Table. For this example, you are using the name production_1 for the current system.
Note that target_system_name is used as the primary index for SystemFE.Opt_Cost_Table and SystemFE.Opt_DBSCtl_Table.
DIAGNOSTIC DUMP COSTS production_1;
For More Information
For more information about environmental costs, see:
For more information about DBS Control flags, see Utilities.