Query Bands and Load Utilities - Teradata Vantage

Teradata® VantageCloud Lake

Deployment
VantageCloud
Edition
Lake
Product
Teradata Vantage
Published
January 2023
ft:locale
en-US
ft:lastEdition
2024-12-11
dita:mapPath
phg1621910019905.ditamap
dita:ditavalPath
pny1626732985837.ditaval
dita:id
phg1621910019905

The term load utilities includes utilities or applications that use the Teradata FastLoad, MultiLoad, and FastExport protocols such as the Teradata Parallel Transport Load, Update, and Export operator, the FastLoad, MultiLoad, and FastExport utilities, and the embedded JDBC versions of FastExport and FastLoad.

You can classify these utilities based on session query bands. Because a transaction query band is discarded when a transaction ends, set a session query band when you use query banding with the data loading utilities if the query band is to be applied to all statements in the utility script.

Client load utilities can set optional reserved query band names to control throttling. Vantage gets information about the name of the utility and the size of the data through these reserved query band names.

For example, a client utility can set the UtilityDataSize query band by means of a script. This sizing information is then used by Vantage as an aid in determining the number of AMP sessions to use for the load job.

The expected values for UtilityDataSize are SMALL, MEDIUM, and LARGE. These values provide Vantage with a simple way to influence the selection of the number of sessions needed to process the load job. The intent is to select a reasonable number of sessions for the default. You can use session configuration rules to provide a more precise selection.

The client utilities do not set the UtilityDataSize query band automatically. Specify UtilityDataSize in a script, as in the following example.

.LOGTABLE Logtable002;
.LOGON tdpx/user,pwd;

 SET QUERY_BAND='UtilityDataSize=LARGE;' UPDATE FOR SESSION;

.BEGIN IMPORT MLOAD TABLES Employee;
..........
.END MLOAD;
.LOGOFF;

Reserved Query Band Names and Values

Do not use any reserved query band name except BINPACKALGO4PARQUET, which sets the binpacking algorithm to use when reading Parquet files (for details, see SET QUERY_BAND Syntax Elements). The others are reserved for use by Teradata-written applications and applications written by third party Teradata partners.
These categories of query bands are reserved for use by Teradata Enterprise Applications and by Teradata partner applications:
  • Load utility query bands
  • Storage management query bands
  • Redrive query bands