Teradata Specific Properties

This section describes the connection properties that are specific to the Teradata data source.

 

Port

Port number for the data source to connect with the host.

The Port number for Teradata is 1025.

Connection URL Pattern

Sends debug log messages to system.out rather than to a file. The pattern is jdbc:teradata://<HOST>/DBS_PORT=<PORT>/DATABASE=<DATABASE_NAME>/CHARSET=UTF8,COMPAT_DBS=true. To view debug messages, append ,LOG=DEBUG (including the initial comma) to the pattern.

Enable FastLoad/FastExport for large tables

Use the FastLoad or FastExport utility to speed up queries. Cardinality information determines whether to use Fastpath or JDBC default loading for a given query.

FastExport Session Count

The number of FastExport sessions to use.

FastLoad Session Count

The number of FastLoad sessions to use.

Query Banding

Turns the query banding feature on (At Session Level) or off (Off). Stores query context information in the Teradata session table so it can be recovered after a system reset. Query banding takes effect when the data source is next used.

Connection pooling has no effect on query band data.

QueryBand Properties

Click QueryBand Properties on the right to open a dialog box in which to specify property-value pairs to store in the session table.

Four properties are available by default. For the first three, if the default value (including brackets) appears alone in the value field, it is replaced with the actual value at run time.

• TDV_USER. ID of the TDV user, application or report that originated the request from a middle-tiered application. The default value is <TDV_USER>.
• DOMAIN. The default value is <DOMAIN>.
• SESSION_NAME. The default value is <SESSION_NAME>.
• SYS. The default value is TDV.

TDV administrator can click Add property to add custom name-value pairs.

Use X Views

Returns data only for rows containing information on objects that the requesting user owns, created, has privileges on, or has been granted access through a current or nested role.

Is dataship source

Indicates whether the physical data source might be used as a source of shipped tables to another data ship enabled data source

Lower bound/Upper bound

TDV uses Explain Plan to arrive at a numeric estimate of the cost of shipping data from a node to the Data Virtualizer. When the cost of shipping a federated query node falls between the limits of the Lowerbound and Upperbound, it is considered eligible for shipment so that it can be processed locally.

Is dataship target

Indicates whether the physical data source might be used to receive shipped tables from another data ship enabled data source.

Schema path for Temp Tables

A relative path to set the location of the temp tables on the data source. It is the name of a schema in the data source.

Temp Table Prefix

A character string addition to temporary table names so that they are recognized if they are needed.