Utility Management - Advanced SQL Engine - Teradata Database

Database Introduction

Product
Advanced SQL Engine
Teradata Database
Release Number
17.10
Published
July 2021
Language
English (United States)
Last Update
2021-07-27
dita:mapPath
jiv1600056352873.ditamap
dita:ditavalPath
jiv1600056352873.ditaval
dita:id
B035-1091
lifecycle
previous
Product Category
Teradata Vantage™
You can manage load utilities such as FastLoad, MultiLoad, FastExport similarly to how you manage SQL requests: by classifying them into workload definitions with throttle limits based on:
  • Utility name
  • “Who” criteria (such as user, account, or queryband)
  • “Where” criteria (the name of the database, table, or view)
For example, you can specify that:
  • User A cannot run more than two FastLoad jobs at the same time
  • Only one MultiLoad job can run at a time against Database XYZ
In addition, using the Viewpoint Workload Designer portlet, you can define rules that control the number of sessions that a load utility can use. To create session configuration rules, specify at least one of the following criteria:
  • Utility name (required)
  • Data size
  • “Who” criteria (for example, user, account, client address, or query band)

and then specify the number of sessions to be used when the criteria are met.

For example, you can specify using:
  • Ten sessions for standalone MultiLoad jobs submitted by Joe
  • Four sessions for JDBC FastLoad from the application called WebApp
If you do not create a session configuration rule or the utility currently running does not meet the rule criteria, then Workload Designer automatically uses default session rules to select the number of sessions based on these criteria:
  • Utility name
  • System configuration (the number of AMPs)
  • Optional data size