A
account
The distinct account name portion of the system account strings, excluding the performance group designation. Accounts can be employed wherever a user object can be specified.
allocation group
(AG) A set of parameters that determine the amount of resources available to the sessions assigned to a PG referencing a specific AG. Has an assigned weight that is compared to other AG weights. An AG can limit the total amount of CPU used by sessions under its control.
C
CLI
Command-line interface
CLIv2
Call-Level Interface, Version 2. A library of routines that enable an application program to access data stored in Teradata Database. When used with network-attached clients, CLIv2 contains the following components:
Version 2 of the CLI interface. A collection of callable service routines that provide an interface to a Teradata Database. The interface between the application program and the MTDP (for network-attached clients) or TDP (for mainframe-attached clients).
column
In the relational model of Teradata SQL, databases consist of one or more tables. In turn, each table consists of fields, organized into one or more columns by zero or more rows. All of the fields of a given column share the same attributes.
CPU
Central processing unit
D
DBA
Database Administrator. Generally, a person responsible for the design and management of one or more databases and for the evaluation, selection, and implementation of database management systems.
DBC
Name of database with Teradata Database system tables.
DBCAREA
A communication structure shared by an application program and CLI. The application uses it to forward control and data information. CLI uses it to return control and data information. An application may use a single DBCAREA or multiple DBCAREAs. CLI retains no knowledge of a particular DBCAREA across multiple CLI calls. CLI is concerned only with the values for DBCAREA that are meaningful to the routine called.
DBQL
Database Query Logging, Database Query Log DBQL is a series of system tables created in the DBC database during Teradata Database installation. Used to track query processing. See Database Administration (B035‑1093) to learn more about the DBQL.
DBQM
Database Query Manager.
DDL
Data Definition Language. Supports manipulating database structures and the Data Dictionary information kept about these structures. In Teradata SQL, the statements and facilities that manipulate database structures (such as CREATE, MODIFY, DROP, GRANT, REVOKE, and GIVE) and the Data Dictionary information kept about those structures. In the typical, pre-relational data management system, data definition and data manipulation facilities are separated, and the data definition facilities are less flexible and more difficult to use than in a relational system.
DML
Data Manipulation Language In Teradata SQL, the statements and facilities that manipulate or change the information content of the database. These statements include SELECT, INSERT, UPDATE, and DELETE.
I
ID
Identifier or Identification.
J
JDBC
Java Database Connectivity An API for the Java programming language that defines how a client can access a database. Provides methods for querying and updating data in a database. Oriented toward relational databases.
M
macro
A file created and stored on Teradata Database and executed in response to a Teradata SQL EXECUTE statement. A set of Teradata SQL statements stored by the Teradata Database and executed by a single EXECUTE statement. Each macro execution is implicitly treated as a transaction.
P
parameter
A variable name in a macro for which an argument value is substituted when the macro is executed.
PDSet
Collection of data, including the resource partition, performance group, allocation group, performance period type, and other definitions that control how the Priority Scheduler manages and schedules session execution.
procedure
Teradata stored procedure. Teradata provides SPL to create stored procedures. A stored procedure contains SQL to access data from within Teradata and SPL to control the execution of the SQL.
Q
query management
The primary function of DWM is to manage logons and queries. This feature examines logon and query requests before they are dispatched for execution within Teradata Database, and may reject logons, and may reject or delay queries. It does this by comparing the objects referenced in the requests to the types of DBA-defined rules.
R
request
In host software, a message sent from an application program to Teradata Database.
resource partition
A collection of prioritized PGs related by user associations. Has an assigned weight that determines the proportion of resources available to that partition relative to the other partitions defined for that Teradata Database.
rule
Rules are the name given to the method used by DWM to define what requests are prohibited from being immediately executed on Teradata Database. That is, the rules enforced by DWM provide the Query Management capabilities.
resource partitions
Resource partitions divide the Teradata Database users into groups based on some use or priority strategy, such as by subject area or type of work.
S
session
Also called a Teradata Database session. A session begins when the user logs on to Teradata Database and ends when the user logs off Teradata Database. In client software, a logical connection between an application program on a host and Teradata Database. The connection permits the application program to send one request at a time to and receive one response at a time from Teradata Database.
statement
A request for processing by Teradata Database. A statement consists of a keyword verb, optional phrases, and operands and is processed as a single entity.
SQL
Structured Query Language
T
table
A set of one or more columns with zero or more rows that consist of fields of related information. A two-dimensional structure made up of one or more columns with zero or more rows that consist of fields of related information. See also target table.
TDWM
A database used with Teradata Workload Analyzer.
TASM
Teradata Active System Management
V
view
An alternate way of organizing and presenting information in a Teradata Database. A view, like a table, has rows and columns. However, the rows and columns of a view are not stored directly by Teradata Database. They are derived from the rows and columns of tables (or other views) whenever the view is referenced.