Download (direct link):
To implement TDQM, the special user/database DBQryMgr must exist. You can create DBQryMgr, or migrate it from a previous version of Teradata RDBMS, using the TDQM Administrator client tool.
You use the TDQM Administrator tool to:
• Enable TDQM
• Define new rules, or modify existing rules, to a Teradata RDBMS on which TDQM is already enabled
• Disable TDQM
The TDQM Administrator creates and stores the rules and limit parameters in the following data tables:
TDQM copies the rules cache to the TDQM.GDO. This object is used to dynamically start and stop TDQM checking based on the current ENABLE/DISABLE setting, and also to immediately rebuild the rules cache after a Teradata RDBMS restart.
15 - 12 Teradata RDBMS Database Administration
Chapter 15: Tools for Managing Resources
Scheduling Workloads with Teradata Dynamic Query Manager (TDQM)
Other chapters in this book, other Teradata RDBMS publications, and client publications offer more details and instructions on using TDQM, as follows:
IF you want information on . THEN see .
how to use TDQM to schedule and control your query workloads Teradata Dynamic Query Manager User Guide.
base workload rules on accounts and Priority Scheduler performance groups • "Accounts and Performance Group Names" on page 5-22 • "Priority Scheduler" in Teradata RDBMS Utilities
how to define, load, and maintain your query validation rules and limits The chapter titled "Teradata Dynamic Query Manager" in Teradata Dynamic Query Manager Administrator Guide.
Teradata RDBMS startup and restart processing Chapter 9: "Stopping and Restarting the System".
TDQM user messages and the DBQLogTbl.ErrorText field "DBQLogTbl" on page 14-7.
how TDQM query checking affects Teradata RDBMS performance Teradata RDBMS Performance Optimization.
15 - 12
Teradata RDBMS Database AdministrationAppendix A:
Teradata RDBMS Configuration, Global Defaults, and Client Connections
This appendix provides an overview of the Teradata RDBMS configuration, the global default controls, and the client connection software, and describes tools you can use to view or change system-wide (global) information, including:
Topics include an overview of the tools used to:
• Display the currently-installed Teradata RDBMS software release and version and, if more than one package is installed, switch from one to another.
• Display or change the database configuration using the:
• System tables and views comprising the Data Dictionary
• Configuration and Reconfiguration utilities
• View or change the global defaults, including:
• International character set support
• Cultural data formatting definitions
• Database (DBS) tunable parameters
• Parallel Database Extension (PDE) hardware configuration and settable parameters
• Gateway network parameters
The client connection sections provide an overview of:
• Client configurations, including channel-connected (mainframe) and network-connected clients.
• How to specify and change session defaults.
• The functions of the mainframe-resident Teradata Director Program (TDP).
• The Teradata Gateway control utilities.
Teradata RDBMS Database Administration
A - 1Appendix A: Teradata RDBMS Configuration, Global Defaults, and Client Connections
Using Data Dictionary Views and Macros
Using Data Dictionary Views and Macros
Use the pre-defined system views to retrieve information about all aspects of Teradata RDBMS, from the definitions of users, databases, roles, profiles, and data entities such as tables, journals, triggers, views, macros, indexes, and stored procedures, to session identification and activity, access rights, active locks, international language character sets, and error logs. The views select the most commonly-referenced columns from the underlying system tables. For a description of each view, see Teradata RDBMS Data Dictionary.
Use the pre-defined system macros to enable security functions, such as executing BEGIN/ END LOGGING and GRANT/REVOKE LOGON statements, and to obtain resource usage reports. For details on using system macros, see Teradata RDBMS Security Administration and Teradata RDBMS Resource Usage Macros and Tables.
Types of System Views
Two sets of the system views are available, with different access rights on each set, as follows:
This version . . . Reports . . .
standard information associated with all applicable users
X only a subset of the available information. These views are defined with a WHERE User=username clause, which returns information only on objects the requesting user owns or on which the user has privileges. These views are also called limited or restricted views. The limited views are identified by the character X, which is appended to the view name (for example, TableSizeX).