Books
in black and white
Main menu
Share a book About us Home
Books
Biology Business Chemistry Computers Culture Economics Fiction Games Guide History Management Mathematical Medicine Mental Fitnes Physics Psychology Scince Sport Technics
Ads

Teradata RDBMS Database Administration - NCR

NCR Teradata RDBMS Database Administration - NCR , 2004. - 616 p.
Download (direct link): teradatadatabaseadmin2004.pdf
Previous << 1 .. 170 171 172 173 174 175 < 176 > 177 178 179 180 181 182 .. 218 >> Next


Managing Resources with Priority Scheduler

IF you want to . THEN use . For more information, see ...
collect processing statistics for post-session comparison and analysis DBQL feature to log query processing behavior On channel-attached clients, the TDPTMON routine to track transaction and response times from and to the TDP ResUsage macros to obtain reports of disk and CPU usage "Applying the Logged Data" on page 14-15 "TDP Transaction Monitor" on page D-14 "ResUsage Reports" on page D-11 "RSSmon Utility" in Teradata RDBMS Utilities (UNIX only) Teradata RDBMS Resource Usage Macros and Tables

Priority Scheduler Administrator (PSA)

PSA is a utility running under Teradata Manager that provides the ability to:

Easily define Priority Scheduler profiles

Generate schmon scripts to implement those profiles.

PSA also provides tools to monitor and control the Priority Scheduler environment.

A Priority Scheduler Profile is the collection of Resource Partitions, Performance Groups, Performance Periods, Allocation Groups, and other scheduler definitions that control how the Priority Scheduler manages and schedules session execution.

The features provided by Priority Scheduler Administrator include:

An easy-to-use GUI for standard use of the schmon utility

Visualization of:

Assigned Priority Scheduler weights

CPU consumption, by Allocation Groups and Resource Partitions

A Priority Scheduler profile configurator, with the ability to set up and save different profiles for different performance windows

Priority Scheduler profile management and scheduling

Enhanced ability to monitor Priority Scheduler performance

Historical records of schmon output that can be charted and reported

Pass scheduling data to the Session Applet of Teradata Manager Service

For details and instructions, see Teradata Manager User Guide.

15 - 10 Teradata RDBMS Database Administration

Chapter 15: Tools for Managing Resources

Scheduling Workloads with Teradata Dynamic Query Manager (TDQM)

Scheduling Workloads with Teradata Dynamic Query Manager (TDQM)

When TDQM is enabled, SQL queries from any supported Teradata RDBMS interface (including, but not limited to, BTEQ, CLIv2, ODBC, JDBC) are validated against user-defined query management rules stored in tables in the user-defined database DBQryMgr.

Note: Unless otherwise specified, TDQM checks every query of every session. You can set up specific users to bypass TDQM checking.

If DBQL is enabled:

If a query is in violation, Teradata rejects the query, returns an error message to the originating session, and inserts a timestamped row in the DBQLogTbl, populating the ErrorCode and ErrorText fields to indicate the type of TDQM rejection.

If a query potentially is to be delayed through Workload limits, sets the TDQMFlag value to T in DBQLogTbl. The difference between the StartTime and the FirstStepTime is the amount of time the query was delayed in the Workload queue.

You can check the contents of the DBQLogTbl.ErrorText field to determine the time the query spent in the delayed state. Also, the TDQM Administrator utility provides real-time statistics on delayed requests.

You enable or disable TDQM through the TDQM Administrator using the menu choices:

ENABLE/DISABLE/QUERY TDQM

For instructions, see Teradata Dynamic Query Manager Administrator Guide and Teradata Dynamic Query Manager User Guide.

TDQM Rules

The supported TDQM rules allow you to set the following limits:

IF you want to . THEN . Results are based on .
control access to database objects Define an 'access' restriction and then link the database objects to be restricted. days and times when the restriction is in effect
control query processing time Define a maximum processing time limit using a 'query resource' restriction and then link the appropriate database objects. Days and times when the restriction is in effect Elapsed time estimated by the optimizer

15 - 12 Teradata RDBMS Database Administration Chapter 15: Tools for Managing Resources

Scheduling Workloads with Teradata Dynamic Query Manager (TDQM)

IF you want to . THEN . Results are based on .
control response rows define a maximum row limit using a 'query resource' rule and then link the database objects to be restricted. Days and times when the restriction is in effect Answer set size estimated by Teradata RDBMS optimizer
limit types of joins or scans define rules on types of joins or full table scans using a 'query resource' restriction and link the database objects to be restricted. Days and times when the restriction is in effect Join and scan processing as determined by the optimizer
limit or delay query processing define a 'workload' rule and then link the user, account, or performance group whose sessions or queries are to be limited or delayed one or a combination of the following: Days and times when the rule is to be in effect Number of sessions running when the query is received
Previous << 1 .. 170 171 172 173 174 175 < 176 > 177 178 179 180 181 182 .. 218 >> Next