Professional Documents
Culture Documents
Administrator Guide
Release 14.00
B035-2511-071A
August 2011
The product or products described in this book are licensed products of Teradata Corporation or its affiliates.
Teradata, BYNET, DBC/1012, DecisionCast, DecisionFlow, DecisionPoint, Eye logo design, InfoWise, Meta Warehouse, MyCommerce,
SeeChain, SeeCommerce, SeeRisk, Teradata Decision Experts, Teradata Source Experts, WebAnalyst, and Youve Never Seen Your Business Like
This Before are trademarks or registered trademarks of Teradata Corporation or its affiliates in the United States and other countries.
Adaptec and SCSISelect are trademarks or registered trademarks of Adaptec, Inc.
AMD Opteron and Opteron are trademarks of Advanced Micro Devices, Inc.
EMC, PowerPath, SRDF, and Symmetrix are registered trademarks of EMC Corporation.
GoldenGate is a trademark of Oracle.
Hewlett-Packard and HP are registered trademarks of Hewlett-Packard Company.
Intel, Pentium, and XEON are registered trademarks of Intel Corporation.
IBM, CICS, RACF, Tivoli, and z/OS are registered trademarks of International Business Machines Corporation.
Linux is a registered trademark of Linus Torvalds.
LSI is a registered trademark of LSI Corporation.
Microsoft, Active Directory, Windows, Windows NT, and Windows Server are registered trademarks of Microsoft Corporation in the United
States and other countries.
NetVault is a trademark or registered trademark of Quest Software, Inc. in the United States and/or other countries.
Novell and SUSE are registered trademarks of Novell, Inc., in the United States and other countries.
Oracle, Java, and Solaris are registered trademarks of Oracle and/or its affiliates.
QLogic and SANbox are trademarks or registered trademarks of QLogic Corporation.
SAS and SAS/C are trademarks or registered trademarks of SAS Institute Inc.
SPARC is a registered trademark of SPARC International, Inc.
Symantec, NetBackup, and VERITAS are trademarks or registered trademarks of Symantec Corporation or its affiliates in the United States
and other countries.
Unicode is a registered trademark of Unicode, Inc. in the United States and other countries.
UNIX is a registered trademark of The Open Group in the United States and other countries.
Other product and company names mentioned herein may be the trademarks of their respective owners.
THE INFORMATION CONTAINED IN THIS DOCUMENT IS PROVIDED ON AN AS-IS BASIS, WITHOUT WARRANTY OF ANY KIND, EITHER
EXPRESS OR IMPLIED, INCLUDING THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR
NON-INFRINGEMENT. SOME JURISDICTIONS DO NOT ALLOW THE EXCLUSION OF IMPLIED WARRANTIES, SO THE ABOVE EXCLUSION
MAY NOT APPLY TO YOU. IN NO EVENT WILL TERADATA CORPORATION BE LIABLE FOR ANY INDIRECT, DIRECT, SPECIAL, INCIDENTAL,
OR CONSEQUENTIAL DAMAGES, INCLUDING LOST PROFITS OR LOST SAVINGS, EVEN IF EXPRESSLY ADVISED OF THE POSSIBILITY OF
SUCH DAMAGES.
The information contained in this document may contain references or cross-references to features, functions, products, or services that are
not announced or available in your country. Such references do not imply that Teradata Corporation intends to announce such features,
functions, products, or services in your country. Please consult your local Teradata Corporation representative for those features, functions,
products, or services available in your country.
Information contained in this document may contain technical inaccuracies or typographical errors. Information may be changed or updated
without notice. Teradata Corporation may also make improvements or changes in the products or services described in this information at any
time without notice.
To maintain the quality of our products and services, we would like your comments on the accuracy, clarity, organization, and value of this
document. Please email: teradata-books@lists.teradata.com.
Any comments or materials (collectively referred to as Feedback) sent to Teradata Corporation will be deemed non-confidential. Teradata
Corporation will have no obligation of any kind with respect to Feedback and will be free to use, reproduce, disclose, exhibit, display, transform,
create derivative works of, and distribute the Feedback and derivative works thereof without limitation on a royalty-free basis. Further, Teradata
Corporation will be free to use any ideas, concepts, know-how, or techniques contained in such Feedback for any purpose whatsoever, including
developing, manufacturing, or marketing products or services incorporating Feedback.
Copyright 2001-2011 by Teradata Corporation. All Rights Reserved.
Preface
Purpose
This book provides information about Teradata Query Scheduler (Teradata QS), which is a
Teradata Tools and Utilities product. Teradata Tools and Utilities are a group of products
designed to work with Teradata Database.
Teradata QS enables the database administrator to manage workloads submitted to the
Teradata Database. This book will help the database administrator (DBA) learn, manage, and
skillfully utilize the Teradata QS features.
Audience
This book is intended for use by:
Other technical personnel who manage both the Teradata QS and Teradata QS server
software programs
Supported Releases
This book supports the following releases:
Go to http://www.info.teradata.com/.
Click Search.
Open the version of the Teradata Tools and Utilities ##.##.## Supported Platforms and
Product Versions spreadsheet associated with this release.
Preface
Prerequisites
The spreadsheet includes supported Teradata Database versions, platforms, and product
release numbers.
Prerequisites
The following prerequisite knowledge is required for this product:
Teradata SQL
Description
August 2011
14.00
Additional Information
Additional information that supports this product and Teradata Tools and Utilities is available
at the web sites listed in the table that follows. In the table, mmyx represents the publication
date of a manual, where mm is the month, y is the last digit of the year, and x is an internal
publication code. Match the mmy of a related publication to the date on the cover of this book.
This ensures that the publication selected supports the same release.
Preface
Additional Information
Type of Information
Description
Access to Information
Release overview
1 Go to http://www.info.teradata.com/.
1 Go to http://www.info.teradata.com/.
Late information
Additional product
information
1 Go to http://www.info.teradata.com/.
2 Under the Online Publications subcategory,
Ordering
information for
manuals
1 Go to http://www.info.teradata.com/.
2 Under Print & CD Publications, click How to
Order.
3 Follow the ordering instructions.
Preface
Additional Information
Type of Information
Description
Access to Information
General information
about Teradata
1 Go to http://www.teradata.com/t/resources.
2 Select a link.
Table of Contents
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3
Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3
Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3
Supported Releases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3
Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4
Changes to This Book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4
Additional Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4
Chapter 1:
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
About the Teradata QS Architecture. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
What Does Teradata QS Do? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
What Are Scheduled Requests? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
How Are Scheduled Requests Processed? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Request Checking. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Job Dispatching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Job Execution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
17
18
18
18
Chapter 2:
Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
System and Software Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Supported Client Operating Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Required Client Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Optional Client Software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Database Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
21
21
21
22
22
Table of Contents
Chapter 3:
Navigate Teradata QS Administrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25
Menu Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25
File Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26
Configuration Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26
Options Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27
Servers Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27
View Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27
Help Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28
Scheduled Requests List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28
Sorting the Scheduled Requests List. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29
Using the Shortcut Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29
Status Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30
Chapter 4:
Prepare the Teradata QS Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .31
Run the TQS Setup Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .31
New Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .31
Upgrade Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .32
Migrate the Teradata QS Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .32
Chapter 5:
Use the Teradata QS Administrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35
Open the Teradata Query Scheduler Administrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35
Open Teradata QS in View-Only Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .36
Exit the Teradata Query Scheduler Administrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .37
Configure the Scheduled Requests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .37
View Teradata QS Server Status. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .37
Configure Execution Time Frames . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .38
Create and Edit Execution Time Frames . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .39
Delete Execution Time Frames . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .40
Set Up Workgroups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .40
Create and Edit Workgroups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .41
Delete Workgroups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .42
Manage Results File Storage. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .42
Save Scheduled Requests Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .43
8
Table of Contents
44
45
45
50
50
51
Chapter 6:
Work with Scheduled Requests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
View Scheduled Requests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Refresh the Scheduled Requests List. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Manage Scheduled Requests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
View SQL Statements for a Scheduled Request. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Change the Execute Time for a Scheduled Job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Execute a Job Immediately . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Delete a Scheduled Request. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Cancel a Job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Delete a Job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Abort a Job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Drop Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
View Job Result Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
55
55
55
56
56
56
57
57
58
58
Appendix A:
About the Dialog Boxes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Refresh Interval Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Results File Storage Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Results File Storage Properties Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Scheduler Profiles Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Workgroups Dialog Box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Workgroup Properties Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Table of Contents
Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .67
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .73
10
List of Figures
11
List of Figures
12
List of Tables
13
List of Tables
14
CHAPTER 1
Introduction
Before using Teradata QS, it may be helpful to read through a product overview. Browse
through these topics to learn more:
Teradata QS
Viewer
Teradata QS
Scheduler/Dispatcher
Teradata QS
Submit Dialog Library
Teradata QS
Server
Processes
Teradata QS
Client Library
Teradata QS
Communications
Library
User
Database(s)
(runs on the
primary server
only)
Teradata QS
Communications
Library
Teradata QS
Database
(4$7-)
Teradata QS
Executor
Program
2496B003
15
Chapter 1: Introduction
About the Teradata QS Architecture
End-users use the Teradata Query Scheduler Submit dialog box to submit single or multiple
SQL statement requests for execution at a later date and time. They also use the Teradata
Query Scheduler Viewer to manage the request results.
The Teradata QS client library has the API for the Teradata QS Viewer. The Teradata QS
communications library handles socket communication with the Teradata QS server.
The DBA configures and views information about the state of the Teradata QS components in
the client/server architecture from the Teradata Query Scheduler Operations utility.
The Teradata Query Scheduler Operations utility is used to manage both the Teradata QS client
and Teradata QS server software programs. The DBA uses the Teradata Query Scheduler
Operations tool to configure and start the Teradata QS server before end-users can schedule
SQL requests.
To learn about the Teradata QS client components, see Teradata Query Scheduler User Guide.
Teradata QS scheduler/dispatcher
The Teradata QS server components save, process, and execute Teradata QS client requests
that have been scheduled.
Teradata QS Administrator
The DBA uses the Teradata Query Scheduler Administrator to enable the scheduled request
feature, set up user profiles, and setup time frames in which schedule requests are executed by
Teradata QS.
Note: The TDWM database is shared by Teradata Dynamic Workload Manager (Teradata
DWM). However, Teradata QS maintains its own tables within the TDWM database. For
more information about Teradata DWM, see Teradata Dynamic Workload Manager User
Guide.
In prior versions of Teradata QS (Teradata DQM), the DBA used the administrator
components to create and manage Teradata Database rules. This function has been moved to
16
Chapter 1: Introduction
What Does Teradata QS Do?
Teradata DWM. Using the Teradata DWM, the DBA can set up rules that manage database
access, increase database efficiency, and enhance workload capacity. Two types of flexible rules
can be created that examine logon and query requests, and that can reject or delay query
requests.
17
Chapter 1: Introduction
How Are Scheduled Requests Processed?
specified. Scheduled requests are subject to the same Teradata Database rule checking as are
interactive requests.
In addition, an execution time frame must be available during the time specified to execute
the request. To learn more about execution time frames, see Configure Execution Time
Frames on page 38.
Scheduled requests are subject to three phases of processing:
Request Checking
Job Dispatching
Job Execution
Request Checking
When a scheduled request is submitted, the Teradata QS server does the following:
Uses the scheduling information the user provides as the intended start time for the
request.
Because a request may not be run until some time after the requested start time, a time
interval in which the request may be run must also be specified.
Checks for an available execution time frame during the specified time period. If no
execution time frames are available, the request is rejected.
Schedules the first job for the request. Unique IDs are generated for the request and its first
job.
Job Dispatching
After the first job is scheduled, the Teradata QS server does the following:
Job Execution
Teradata QS server follows these steps when attempting to run a scheduled request job:
18
If a results table/file was specified and the results table/file currently exists, the job fails
unless the user specified that the results could be deleted.
Reschedules the job for at least 15 minutes later if a Teradata Database workload
management restriction is encountered.
Chapter 1: Introduction
What Can I Do with Teradata QS?
If a results table/file was specified, the last statement of the scheduled request is first run in
prepare mode to obtain the column types and names of the result data. If necessary, the
result table/file is recreated with those column types, and the last statement (which must
be a SELECT statement) is run. The result data is written to the results table/file.
Create, delete, or modify time periods (called execution time frames) when scheduled
requests are executed by Teradata QS.
Create, delete, or modify workgroups that equitably distribute resources and scheduled
requests workloads during execution time frames.
Create, delete, or modify the locations where scheduled request results files are stored and
accessed by all Teradata QS servers.
Create, delete, or modify sets of scheduled request attributes (called profiles) for users,
accounts, DBS roles, and DBS profiles.
View, execute, cancel, immediately submit, abort, delete, or modify scheduled SQL
requests and jobs to avoid adversely affecting a Teradata Database during prime usage
periods.
See Chapter 5: Use the Teradata QS Administrator to learn how to use these features. For
detailed descriptions of the controls in this interface, see Chapter 3: Navigate Teradata QS
Administrator
Teradata QS has a view-only mode that allows users to log on without being an administrator.
In view-only mode, the user can view Teradata QS settings, but cannot make changes. For
more information on logging on in view-only mode, see Open the Teradata Query Scheduler
Administrator on page 35. For a detailed description of the functionality of Teradata QS in
view-only mode, see View-Only Mode on page 51.
19
Chapter 1: Introduction
How Do I Get Help?
Scheduler Operations tools to configure and start the Teradata QS server before end-users can
schedule SQL requests.
For instructions on starting the Teradata QS Server, see Teradata Query Scheduler User Guide.
The Help window opens. Use the tools available from the Help window to navigate to other
topics.
To allow online help content to appear using Internet Explorer, version 7.0
Use this procedure if a warning appears such as, To help protect your security, Internet Explorer
has restricted this webpage from running scripts or ActiveX controls that could access your
computer.
20
Under Security, click Allow active content to run in files on My Computer*, and click OK.
Close and then reopen Microsoft Internet Explorer for this change to take effect.
CHAPTER 2
Prerequisites
Before using Teradata QS, make sure your system is set up correctly. Also set up a Teradata
CLIv2 (Call-Level Interface version 2) connection. Browse through the following topics to
learn more:
For detailed installation information, see Teradata Tools and Utilities Installation Guide for
Microsoft Windows.
Database Requirements
TCP/IP driver with WinSock support for Windows version 1.1 or later
21
Chapter 2: Prerequisites
Modify the HOSTS File
Database Requirements
Prior to running Teradata Query Scheduler 14.00, run the tqssetup.bteq script. The script
installs important updates to the TDWM database. Teradata Query Scheduler 14.00 requires
Teradata Database V2R6.1 or later.
Open Windows Explorer and navigate to the HOSTS file in the subdirectory of the
directory in which Windows is installed.
Add the IP address and the Teradata Database name with the COP1 suffix.
22
Chapter 2: Prerequisites
Verify the Network Connection
2
In the Open text box, type the PING command followed by the name of the Teradata
Database and the COP1 suffix. For example: PING ssscop1
Where sss is the Teradata Database to connect to.
If the PING command does not receive a successful response from the network, see the
network administrator to determine the cause.
23
Chapter 2: Prerequisites
Verify the Network Connection
24
CHAPTER 3
Before using Teradata QS Administrator, familiarize yourself with the GUI (graphical user
interface).
After verifying that the system is set up and configured correctly, the Teradata Query
Scheduler Administrator (Figure 2) is ready for use. The basic features of the Teradata Query
Scheduler Administrator interface are:
The Menu Bar, located immediately below the title bar, is used to access all of the Teradata
Query Scheduler Administrator commands.
The Scheduled Requests List, located below the menu bar, shows all users scheduled
requests and jobs.
The Status Bar, located at the bottom of the window, shows information about the
database status.
See Chapter 5: Use the Teradata QS Administrator and Chapter 6: Work with Scheduled
Requests to find out about using the Teradata Query Scheduler Administrator.
To get familiar with the Teradata QS Administrator dialog boxes, see Appendix A: About the
Dialog Boxes.
Menu Bar
Use the menu bar in the Teradata Query Scheduler Administrator (Figure 3) to access all
functions and features in Teradata QS. Use your mouse or keyboard to select the commands in
these menus:
25
File Menu
Configuration Menu
Options Menu
Servers Menu
View Menu
Help Menu
File Menu
The following table describes the commands of the File menu.
Table 1: File Menu
Command
Description
Exit
Disconnects from the Teradata Database and closes the Teradata Query
Scheduler Administrator.
Configuration Menu
The following table describes the commands of the Configuration menu:
Table 2: Configuration Menu
26
Command
Description
Scheduler Profiles
Set up groups of users, accounts, DBS roles, and DBS profiles that are associated
with Teradata QS profiles.
Workgroups
Results File
Storage
Execution Time
Frames
Enable/Disable
Scheduling
Options Menu
The following table describes the commands of the Options menu:
Table 3: Options Menu
Command
Description
Cancel Job
Terminates a job with a Waiting status selected from the Scheduled Requests list.
Modify Execute
Time
Specify a new schedule execution date and time for a job with a Waiting status
selected from the Scheduled Requests list.
Execute Now
Immediately run a job with a Waiting status selected from the Scheduled
Requests list. Or immediately re-execute a job selected from the Scheduled
Requests list that has failed for any reason.
Abort Job
Terminate a job with an Executing status selected from the Scheduled Requests
list.
Delete Request
Remove the request selected from the Scheduled Requests list and all the related
jobs.
Delete Job
Drop Results
Eliminate the results table or file for the job or request selected from the
Scheduled Requests list.
Job Information
Show all of the data concerning how a job completed, such as rows returned,
processing time, and more.
Show SQL
Show the SQL statements for the job selected from the Scheduled Requests list.
Servers Menu
The following table describes the commands of the Servers menu:
Table 4: Servers Menu
Command
Description
Server Status
View the condition of all Teradata QS servers in the Query Scheduler Server
Status dialog box.
View Menu
The following table describes the commands and submenus of the View menu:
Table 5: View Menu
Command
Submenu
Description
Refresh
Now
27
Command
Submenu
Description
Interval
Font
Select the font for displaying the list of scheduled requests, the request
SQL, and Teradata QS object names (Workgroups, File Storage areas,
and so on) in the Font dialog box.
Help Menu
The Help menu has commands that provide access to online help and information about the
version of the software installed on your computer.
The following table lists the commands for the Help menu:
Table 6: Help Menu
Command
Description
Help Topics
About Teradata QS
Administrator
28
Column Header
Description
Request Name
The name assigned to the job when it was submitted using the Teradata Query
Scheduler Submit dialog box.
Request ID
Job ID
Scheduled
User Name
Status
Information
Details about how the job completed, such as rows returned, processing time,
database errors, and result file errors.
29
Status Bar
The status bar at the bottom of the Teradata Query Scheduler Administrator (Figure 5) shows
the following information:
Table 8: Status Bar
Option
Description
Status
Database Time
Database Date
Time frame
30
CHAPTER 4
After Teradata Query Scheduler 14.00 has been installed per instructions from Teradata Tools
and Utilities Installation Guide for Microsoft Windows, the DBA runs a script to create
scheduling tables for the TDWM database. This chapter provides the following topics:
New Installation
Upgrade Installation
New Installation
To run Teradata QS on a new installation of the Teradata Database (that is, one on which an
earlier version of Teradata QS or Teradata DQM has not been installed), run the tqssetup.bteq
script. The script creates scheduling tables in the TDWM database that Teradata QS uses to
store scheduling information.
In the .logon statement, replace dbsName with the name of the Teradata Database whose
tables you are upgrading to 14.0.
Execute the script using BTEQ. See Basic Teradata Query Reference for instructions.
After the tqssetup.bteq script has completed processing:
31
From the Query Scheduler Administrator main window, enable scheduling, configure
time frames, file storage, workgroups, and profiles. See:
Restart the Operations utility if prompted to do so, and then restart the server. After
the server has started, in the Scheduler Viewer (client) application, use the Connect
command to connect to a Teradata QS Server, and the Schedule SQL command to
submit scheduled requests.
Upgrade Installation
Teradata QS 14.00 supports upgrades from Teradata QS versions 6.1, 6.2, 12.0, 13.0, and
13.10. Follow the instructions from Run the TQS Setup Script on page 31 to upgrade the
scheduling tables by running the tqssetup.bteq script.
Install the Teradata QS 14.00 Administrator package. (The client and server packages can
also be installed at this time.) For instructions, see the Teradata Tools and Utilities
Installation Guide for the appropriate operating system.
32
First upgrade from Teradata 6.0 to 12.0, as described in the section Migrating the
Teradata QS Database of Teradata Query Scheduler Administrator Guide, version 12.00.
Note: You must perform the upgrade and migration to 12.0 before continuing.
Upgrade from Teradata QS 12.0 to Teradata 14.00 using the tqssetup.bteq script. See Run
the TQS Setup Script on page 31.
33
34
CHAPTER 5
After setting up or migrating your Teradata QS database, begin using the Teradata QS
Administrator.
Configure the scheduled requests feature using the Teradata Query Scheduler Administrator,
as well as manage scheduled request, user profiles, and execution time frames. Browse through
these topics to learn more:
Set Up Workgroups
35
Complete the following options in the Teradata Query Scheduler Admin Logon dialog box:
Table 9: Teradata Query Scheduler Admin Logon Dialog Box Description
Option
Description
Enter the name of the Teradata Database to use for scheduled SQL
requests.
Password box
Enter the password associated with the user specified in the User Name
box.
Parameter box
Click OK.
Teradata QS Administrator connects the Teradata Database and displays the list of
scheduled requests.
To disconnect from the Teradata QS database and exit the Teradata Query Scheduler
Administrator, see Exit the Teradata Query Scheduler Administrator on page 37.
36
Enter the database name and the associated user name and password. For more
information on the remaining options, see Table 9 on page 36.
When logged onto Teradata QS as a non-administrator (user name other than tdwm),
Teradata QS opens in view-only mode. For more information on the functionality in viewonly mode, see View-Only Mode on page 51.
The Teradata QS server disconnects and the Teradata Query Scheduler Administrator
closes.
37
Note: Delete is available only after selecting an item from the Servers list.
2
Click Close to exit the Teradata QS Server Status dialog box and return to the Teradata QS
Administrator.
Click Delete.
Information about that server is removed from the tables in the TDWM database.
Click Close to exit the Query Scheduler Server Status window and return to the Teradata
Query Scheduler Administrator.
38
After creating an execution time frame, the DBA must make it available on your Teradata
Database system. Scheduled requests are not accepted or run unless an execution time frame is
available.
When a user submits a request for scheduling, Teradata QS determines whether there are any
execution time frames available during the scheduled time period. If no execution time frames
are available and the maximum start interval is exceeded, then the request is not scheduled.
Although multiple execution time frames can be created and enabled, only the primary
Teradata QS server actually dispatches and executes the scheduled requests.
To modify an existing time frame, select the desired time frame from the Time Frame
Names list, and then click Edit. Go to Step 4.
Note: The Edit and Delete buttons are available only when a time frame is selected
from the list.
Type the name of the new time frame in the Time Frame Name box. Time frame names
cannot contain single quotes.
Note: If editing an execution time frame, the Time Frame Name box is read-only.
39
Select the Enable Time Frame check box to make the time frame available. (By default,
this control is not selected.)
Clear the Enable Time Frame check box to make the time frame unavailable.
To make the time frame effective each day of the week, leave the Everyday check box
selected. (By default, this control is selected.)
To select specific days when the time frame is in effect, clear the Everyday check box
and select the desired days using the boxes in the Days frame.
Using a 24 hour format, enter the hour the time frame is to begin in the From box.
Click OK to save your entries and close the Time Frame Properties dialog box.
The new time frame appears in the Time Frame Names list in the Execution Time Frames
dialog box.
Click Close to close the Execution Time Frames dialog box and return to the Teradata
Query Scheduler Administrator.
Select the time frame to delete from the Time Frame Names list.
Click Delete.
Click Yes to confirm the deletion and close the message box.
The time frame no longer appears in the Time Frame Names list.
Click Close to close the Execution Time Frames dialog box and return to the Teradata
Query Scheduler Administrator.
Set Up Workgroups
A workgroup represents a collection of related scheduled requests for a number of users,
accounts, roles, and profiles. The DBA can create, edit, or delete any number of workgroups
that equitably distribute resources and scheduled requests workloads during execution time
frames.
Assign a maximum number of requests that can be simultaneously executing from each
workgroup. This ensures that a fair share of the scheduled work gets done within the
execution time frames for all workgroups.
40
Click Configuration>Workgroups.
The Workgroups dialog box appears with DEFAULT_WORKGROUP in the Workgroup
Names list.
Note: When creating or modifying a scheduled requests profile for a user, user group, or
account, select a workgroup to associate with the profile. See Manage Scheduler Profiles
on page 44 for more information.
2
To modify an existing workgroup, select the desired workgroup from the Workgroup
Names list, and then click Edit. Go to Step 4.
Note: The Edit and Delete buttons are available only after a workgroup is selected from
the list.
Type up to 30 characters for the name of your workgroup in the Workgroup Name box.
Note: If editing a workgroup, the Workgroup Name box is read-only.
In the Maximum queries running simultaneously box, enter a number between 0 and 28 to
limit the number of concurrent queries that can be run by this workgroup.
Click OK to save your entries and close the Workgroup Properties dialog box.
The workgroup appears in the Workgroup Names list in the Workgroups dialog box.
Click Close to close the Workgroups dialog box and return to the Teradata Query
Scheduler Administrator.
41
Delete Workgroups
When deleting a workgroup, make sure it is not being referenced by a scheduler profile. If it is,
change the scheduler profile to reference a different work group or delete the scheduler profile.
To change the scheduler profile, Manage Scheduler Profiles on page 44. To delete the
scheduler profile, see Delete Scheduler Profiles on page 50.
To delete a workgroup
1
Click Configuration>Workgroups.
The Workgroups dialog box appears.
Click Delete.
Click Yes to confirm the deletion and close the message box.
The workgroup no longer appears in the Workgroup Names list in the Workgroups dialog
box.
Click Close to close the Workgroups dialog box and return to the Teradata Query
Scheduler Administrator.
42
Ensure all disk drives on which results files are stored by Teradata QS servers are identically
available to all Teradata QS server systems on Windows. This enables any Scheduled
Request client to connect to any Teradata QS Server to retrieve their results.
Ensure all results file storage locations are configured so they have the same path on all
server systems. This is easier to manage than configuring a different results location for
every server.
Configure the Teradata QS Server to run as a user with network access privileges and write
and read access to the specified directory.
From the list of services, select TQS Server and click Properties or right-click and select
Properties from the shortcut menu.
In the TQS Server Properties dialog box, click the Log On tab.
Click This Account and fill in the domain/username and password boxes.
Note: Be sure the user specified is a member of the Windows Administrators group.
To modify an existing file storage location, select the name from the File Storage
Names list, and then click Edit. Go to Step 4.
43
Note: The Edit and Delete buttons are available only after a name is selected from the
list.
Type a name for the results file storage in the Results File Storage box.
Note: If editing a file storage location, the Results File Storage box is read-only.
Type the directory where this file storage is to be located in the Windows Results Directory
box.
Click OK to save your entries and close the Results File Storage Properties dialog box.
The storage location appears in the File Storage Names list in the Results File Storage
dialog box.
Click Close to exit the Results File Storage dialog box and return to the Teradata Query
Scheduler Administrator.
Select the file storage location that will be deleted from the File Storage Names list.
Note: The Edit and Delete buttons are available only after selecting a file storage location
from the list.
Click Delete.
Click Yes to confirm the deletion and close the message box.
The storage location no longer appears in the File Storage Names list in the Results File
Storage dialog box.
Click Close to close the Results File Storage dialog box and return to the Teradata Query
Scheduler Administrator.
44
Automatic Cleanup
Using the Job History box in the profile, specify the length of time that records of scheduled
request jobs will be saved before being automatically deleted from the system. Users can also
delete their own completed jobs at any time.
Using the Results Duration box in the profile, specify the length of time that the users results
data tables and files can be kept, if not updated, before being automatically deleted by
Teradata QS.
From the Select Type list, choose one of the following types of scheduler profiles to create:
Account
Profile
Role
User
The Scheduler Profile Properties dialog box appears with the Scheduling tab selected by
default.
45
Option
Description
Profile Type
(Read-only) See the profile type chosen from the Select Type list on the
Scheduler Profiles dialog box.
Name
(Read-only) See the name of the Teradata Database object selected from
the Objects list on the Scheduler Profiles dialog box.
Allowed Scheduling
Select the types of query requests that can be scheduled by this profile:
No scheduling: Disables scheduling. No requests can be scheduled,
effectively disabling the feature for this user, group, or account.
Onetime only: Runs the request once.
Onetime & Recurring: Runs the request more than once such as daily,
weekly, or monthly.
Workgroup
46
Option
Description
Start Interval
Specify the greatest length of time from the submitted start time that a job
can begin to run in days and hours. Default value is one day.
New requests are not accepted if there is no time between the start time
and the maximum start interval that a request can execute due to rules
and/or unavailability of an execution time frame.
Job History
Specify the number of days between 1 and 365 that job records are
retained before Teradata QS automatically deletes them.
Complete the following options in the Results Tables/Files tab to set up results parameters:
47
Option
Description
Allowed Results
Type
Specify the name of the results database to use as the default. This is the name
of the database in which the Teradata QS Server stores the results. This option
cannot be used if Save in file was selected as the Allowed Results Type.
Create as
Fallback
Specify that the results table is created with the fallback attribute. This option
cannot be used if Save in file was selected as the Allowed Results Type.
Create as
Multiset
Specify that the results table is created with the multiset attribute. This option
cannot be used if Save in file was selected as the Allowed Results Type.
Append user
name
Have Teradata QS to automatically append the user name to the results table.
This option cannot be used if Save in file was selected as the Allowed Results
Type.
Note: When the same results database is used by multiple users, the results
table name is modified to include the user name to avoid duplicates if this
check box is selected.
Specify a relative path beneath the results file storage location where results
from this profile are stored. The Teradata QS Server joins the directory
corresponding to the selected results file storage path and this relative path to
form the full directory path where results are stored. This option cannot be
used if Save in database was selected as the Allowed Results Type.
Field Separator
Character
Select the character to use to separate record fields when results are saved in a
file. This option cannot be used if Save in database was selected as the Allowed
Results Type.
Specify the greatest number of bytes (in thousand bytes) allowed for a results
file. This option cannot be used if Save in database was selected as the Allowed
Results Type.
Results Duration Specify the number of days between 1 and 365 that results tables or files are
retained before they are automatically deleted by Teradata QS. The timestamp
for results is reset when the results are replaced or appended to.
48
Option
Description
Allow users to modify the maximum start interval in the Query Scheduler
Submit dialog box.
Modify results
database name
Allow users to modify the results database in the Query Scheduler Submit
dialog box.
Allow users to modify the Field Separator character for results files in the
Query Scheduler Submit dialog box when saving results to a file.
Click OK.
10 Click Close to close the Scheduler Profiles dialog box and return to the Teradata Query
Scheduler Administrator.
49
Click Delete.
A message box appears prompting confirmation of the deletion.
Click Close to exit the Scheduler Profiles dialog box and return to the Teradata Query
Scheduler Administrator.
Click Cleanup.
Click Close to exit the Scheduler Profiles dialog box and return to the Teradata Query
Scheduler Administrator.
Teradata QS finds and deletes all scheduler profiles associated with Teradata Database
objects that no longer exist.
50
View-Only Mode
View-only mode allows users, other than TDWM admin, to log on to Teradata QS
Administrator and view settings. In view-only mode, the user can open Teradata QS
Administrator, view the settings, but cannot make changes. The following section explains the
functions for view-only mode.
Table 13: Teradata QS Administrator Functions in View-Only Mode
Function
Sub Menu
Logon dialog
None
Configuration Scheduler
Profiles
TDWM can create, edit and delete scheduler profiles. View-only users
can only view the existing settings.
View replaces Edit in view-only mode.
View opens the Scheduler Profile Properties dialog so existing profiles
can be viewed. View is available if an item from the drop down menu
has an existing scheduler profile.
Workgroups
TDWM can create, edit and delete workgroups. View-only users can
only view the settings in workgroups.
View replaces Edit for users other than TDWM. Description: Opens
the Workgroup Properties dialog box where an existing workgroup can
be viewed.
Workgroup Properties Dialog Box: all options are read-only for users
other than TDWM.
Results File
Storage
TDWM can create, edit and delete results file storage. View-only users
can only view the existing settings.
View is available in view-only mode. View opens the Results File
Storage Properties dialog to view an existing file storage mapping.
View replaces the Edit in view-only mode.
Execution
TDWM can create, edit and delete time frames. View-only users can
Time Frames only view these settings.
Options
None
Server
Server
Status
View-only users can see the Teradata QS Server status, but Delete is
available only to the TDWM user.
51
Function
Sub Menu
View
Refresh
Font
None
The items under the Help menu are available in view-only mode.
Help
52
CHAPTER 6
The Teradata Query Scheduler Administrator offers a number of features that help to manage
scheduled requests, user profiles, and execution time frames. Browse through these topics to
learn more:
For instructions, see Open the Teradata Query Scheduler Administrator on page 35.
After connecting to the Teradata Database, all scheduled requests are retrieved and appear
in the Scheduled Requests list of the Teradata Query Scheduler Administrator. (See
Figure 4 on page 29).
View the following information for each of the scheduled jobs currently in the system:
Table 14: Scheduled Requests List: Teradata Query Scheduler Administrator
Column Name
Description
Request Name
The name assigned to the request when it was submitted using the Teradata
Query Scheduler Submit dialog box.
Request ID
Job ID
Scheduled
User Name
Status
Information
Details about how the job completed, such as rows returned, processing
time, database errors, and result file errors.
53
The Scheduled Requests list is updated with information from the Teradata QS server.
Refresh Rate
For information about the Refresh Interval dialog box, see Appendix A: About the Dialog
Boxes.
2
Click the Minute or the Hour option to set the refresh rate.
Click OK to close the Refresh Interval dialog box, and return to the Teradata Query
Scheduler Administrator.
Begin working with the scheduled jobs and requests. To learn more, see Manage
Scheduled Requests on page 55.
54
From from the Scheduled Jobs list of the Teradata Query Scheduler Administrator, select a
job.
Right-click the job to display a shortcut menu and click Show SQL.
The Show SQL dialog box appears showing the SQL statements used in the request.
3
View the information and click OK to close the Show SQL dialog box and return to the
Teradata Query Scheduler Administrator.
From the Scheduled Requests list of the Teradata Query Scheduler Administrator, select a
job with a Waiting status.
Right-click the job to display a shortcut menu and click Modify Execute Time.
Enter a new start time using the Hour and Minute boxes.
Click OK to close the dialog box and return to the Teradata Query Scheduler
Administrator.
55
From the Scheduled Requests list of the Teradata Query Scheduler Administrator, select a
job with a Waiting status or any job that failed to execute.
Right-click the job to display a shortcut menu, and click Execute Now.
A Teradata Query Scheduler Administrator dialog box appears asking for confirmation.
3
Click Yes to confirm the execution, close the dialog box, return to the Teradata Query
Scheduler Administrator, and execute the query.
To delete a request
1
From from the Scheduled Requests list of the Teradata Query Scheduler Administrator,
select a request.
Right-click the request to display a shortcut menu and click Delete Request.
A Teradata Query Scheduler Administrator dialog box appears asking for confirmation.
3
Click Yes to confirm the deletion and close the dialog box.
A Teradata Query Scheduler Administrator message appears indicating the request was
deleted.
Click OK to close the dialog box and return to Teradata Query Scheduler Administrator.
Cancel a Job
Use the Cancel Job command, to cancel the scheduled execution of any selected job in a
Waiting status.
56
After a job is cancelled, it cannot be restarted. If the job is for a recurring request, a new job is
automatically generated by Teradata QS server before the next day. Otherwise, a new
scheduled request must be submitted.
To cancel a job
1
From from the Scheduled Requests list of the Teradata Query Scheduler Administrator,
select a job in a Waiting status.
Right-click the job to display a shortcut menu and click Cancel Job.
A Teradata Query Scheduler Administrator dialog box appears asking for confirmation.
3
Click Yes to confirm the cancellation and close the dialog box.
Admin Cancelled appears under the Status column of the Jobs list in the Teradata Query
Scheduler Administrator for the cancelled job.
Delete a Job
Use the Delete Job command to delete any job that has completed successfully or
unsuccessfully.
If a completed job is deleted for a recurring request, the scheduled request is still available in
the system.
Deleting completed jobs allows for faster updates of the Scheduled Requests list. Jobs are also
periodically deleted as specified using the Teradata Query Scheduler Administrator.
To delete a job
1
From from the Scheduled Requests list of the Teradata Query Scheduler Administrator,
select any completed job.
Right-click the job to display a shortcut menu and click Delete Job.
A Teradata Query Scheduler Administrator dialog box appears asking for confirmation.
3
Click Yes to confirm the deletion and close the dialog box.
A Teradata Query Scheduler Administrator message appears indicating the job was deleted.
Click OK to close the dialog box and return to Teradata Query Scheduler Administrator.
Abort a Job
Use the Abort Job command to terminate any job with an Executing status. For example, abort
a job because the job is tying up Teradata Database resources.
57
To abort a job
1
From from the Scheduled Requests list of the Teradata Query Scheduler Administrator,
select a job with an Executing status.
Right-click the job to display a shortcut menu and click Abort Job.
Click Yes to confirm the deletion and close the dialog box.
Drop Results
Use the Drop Results command to drop the results table or file associated with the selected
request or job. Dropping results cleans up tables or files generated for that request or job.
To use the same results table or file for each request, the results must be dropped. The Drop if
exists or Append if exists options can also be used to drop results when scheduling requests.
For information on that option, see Teradata Query Scheduler User Guide.
To drop results
1
From from the Scheduled Requests list of the Teradata Query Scheduler Administrator,
select a job.
Right-click the request to display a shortcut menu and click Drop Results.
A Teradata Query Scheduler Administrator dialog box appears confirming the deletion.
3
Click Yes to confirm the deletion, close the dialog box, and return to Teradata Query
Scheduler Administrator.
The results of the scheduled request are dropped and have been removed from the TDWM
database.
From from the Scheduled Requests list of the Teradata Query Scheduler Administrator,
select a job.
58
Right-click the job to display a shortcut menu and click Job Information.
A Job Result Information message appears displaying the entire job information text.
Click OK to close the message box and return to the Teradata Query Scheduler
Administrator.
59
60
APPENDIX A
While working with Teradata QS Administrator, information about the options and controls
is available. The following topics provide information about the various dialog boxes:
View>Refresh>Interval.
Figure 6: Refresh Interval Dialog Box
Option/Control
Description
61
Option/Control
Description
Enter a value for the rate at which the Teradata QS Administrator will
update the Scheduled Requests list: 0 to 60 minutes, or 0 to 24 hours.
Enter an interval between 5 and 99 for the rate at which the Teradata QS
server will update the Scheduled Jobs list.
Minute option
Hour option
OK
Cancel
62
Option
Description
Option
Description
New
Creates a new file storage mapping in the New Results File Storage dialog
box.
Delete
Edit
Opens an existing file storage mapping for editing in the Edit Results File
Storage.
Close
Option/Control
Description
Defines the name of the results file storage. The names is limited to 30
characters.
Windows Results
Directory
Defines the Windows directory where the results are saved. The directory
name is limited to 128 characters.
OK
Saves entries and closes the Results File Storage Properties dialog box.
Cancel
Closes the Results File Storage Properties dialog box without saving
entries.
63
Configuration>Scheduler Profiles.
If logged on to Teradata QS in View Mode, the Scheduler Profiles dialog box opens, but no
changes can be made. In View-Only mode, use the View button to view profiles.
Figure 9: Scheduler Profiles Dialog Box
Option/Control
Description
Defines the type of scheduler profile to create. Select one of the following
items:
Account
Profile
Role
User
When an item is selected, an alphabetical list of all available accounts,
profiles, roles, or users appears. Scroll down the list and click the correct
name.
Profile
64
Option/Control
Description
New
Create a profile for the selected account, profile, role, or user. New is
available if the selected account, profile, role, or user does not have an
existing profile.
Delete
Edit
Modify the profile with the changes made. Edit is available if the selected
account, profile, role, or user has an existing profile.
Cleanup
Finds and deletes the Teradata QS profiles for all Teradata Database
objects that no longer exist.
View
Close
Configuration>Workgroups.
If logged on to Teradata QS in View Mode, the Workgroups dialog box opens, but no
changes can be made. In View-Only mode, use the View button to view workgroups.
Figure 10: Workgroups Dialog Box
65
Option
Description
Workgroup Names
New
Delete
Edit
Opens the selected workgroup for editing in the Edit Workgroup dialog
box.
View
Close
66
Option/Control
Description
Workgroup Name
OK
Cancel
Glossary
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.
ANSI American National Standards Institute. The private, non-profit organization
responsible for approving US standards in many areas, including computers and
communications.
API Application Program Interface. An interface (calling conventions) by which an
application program accesses an operating system and other services. An API is defined at
source code level and provides a level of abstraction between the application and the kernel
(or other privileged utilities) to ensure the portability of the code. A language and message
format used by an application program to communicate with the operating system or some
other control program such as a database management system (DBMS) or communications
protocol.
An API can also provide an interface between a high level language and lower level utilities
and services written without consideration for the calling conventions supported by compiled
languages. In this case, the API may translate the parameter lists from one format to another
and the interpret call-by-value and call-by-reference arguments in one or both directions.
ASCII American Standard Code for Information Interchange. The basis of character sets
used in almost all present-day computers.
B
BTET Begin Transaction End Transaction. The Transaction mode (option TRANSACT or
-tr) that implicitly creates transactions for each SQL request if there is not an active
transaction. Commands that mark a unit of work that is all updated or all rolled back (not
updated).
BTEQ Basic Teradata Query. A general-purpose, command-based program that allows users
on a workstation to communicate with one or more Teradata Database systems, and to format
reports for both print and screen output.
C
CLIv2 Call-Level Interface version 2. The application used by Teradata DWM to connect to
the Teradata Database.
CLI2SPB CLIv2 system parameter block (SPB) for network-attached systems. The internal
SPB, is a data structure that is examined during initialization. During initialization, any
67
Glossary
DBCAREA values not set in the clispb.dat file by the user will default to the values contained
in CLI2SPB.
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 The default database associated with user DBC. When Teradata Database is first
installed on your server, it has only one user. This user is called User DBC and it owns all other
databases and users in the system.
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.
DBS
A Database system
DNS Domain Name System. A general-purpose distributed, replicated, data query service
chiefly used on Internet for translating hostnames into Internet addresses. Also, the style of
hostname used on the Internet, though such a name is properly called a fully qualified domain
name. DNS can be configured to use a sequence of name servers, based on the domains in the
name being looked for, until a match is found.
E
exclusion join In Teradata SQL, a product join or merge join where only the rows that do
not satisfy (are NOT in) the conditional specified in the SELECT are joined.
execution time frame A period of time when Teradata DWM can execute scheduled
requests that are waiting to run.
G
GSS Generic Security Services. An application level interface (API) to system security
services. It provides a generic interface to services which may be provided by a variety of
different security mechanisms. Vanilla GSS-API supports security contexts between two
entities (known as principals).
I
ID
Identifier or Identification.
inner join In Teradata SQL, a join operation on two or more tables, according to a join
condition, that returns the qualifying rows from each table.
68
Glossary
J
job
join In Teradata SQL, a join is a SELECT operation that allows columns and rows to be
combined from two or more tables to produce a result. Join types restricted by Teradata DWM
are inner join, outer join, merge join, product join, and all joins. For more information, see all
joins, exclusion join, inner join, merge join, nested join, and RowId join.
M
merge join In Teradata SQL, the type of join that occurs when the WHERE conditional of a
SELECT statement causes the system first to sort the rows of two tables based on a join field
(specified in the statement), then traverse the result while performing a merge/match process.
N
nested join In Teradata SQL, this join occurs when the user specifies a field that is a unique
primary index on one table and which is in itself an index (unique/non-unique primary or
secondary) to the second table.
O
ODBC Open Database Connectivity. An application that may be used by Teradata Tools and
Utilities to establish a connection with a Teradata Database.
outer join In Teradata SQL, an extension of an inner join operation. In addition to
returning qualifying rows from tables joined according to a join condition (the inner join), an
outer join returns non-matching rows from one or both of its tables. Multiple tables are joined
two at a time.
P
performance groups A performance group is a collection of parameters used to control and
prioritize resource allocation for a particular set of Teradata Database sessions within the
Priority Scheduler. Every Teradata Database session is assigned to a performance group during
the logon process. Performance groups are the primary consideration in partitioning the
working capacity of the Teradata Database. To learn more about performance groups, see the
Priority Scheduler section of Utilities.
product join In Teradata SQL, the type of join that occurs when the WHERE conditional of
a SELECT statement causes the Teradata Database system to compare all qualifying rows from
one table to all qualifying rows from the other table. Because each row of one table is
compared to each row of another table, this join can be costly in terms of system performance.
Note that product joins without an overall WHERE constraint are considered unconstrained
(Cartesian). If the tables to be joined are small, the effect of an unconstrained join on
performance may be negligible, but if they are large, there may be a severe negative effect on
system performance.
69
Glossary
profiles A profile is a set of parameters assigned to a user, group of users, or an account that
determines what scheduling capabilities are available and how your Teradata Query Scheduler
scheduled requests server handles their scheduled requests.
R
request A message sent from an application program, such as Teradata DWM, to the
Teradata Database. In the Teradata Query Scheduler schedule request environment, a request
is the definition of the parameters and text associated with a schedule request.
results table/file In the Schedule Request environment, a results table or file is a database
table or a Windows file into which result data for a schedule request that is not self-contained
are stored.
results file storage A symbolic name to a root directory where scheduled requests results are
stored. A file storage location is mapped to a Windows root directory where results are stored.
RowID join In Teradata SQL, this join occurs when one of the join tables has a non-unique
primary index constant, and another column of that table matches weakly with a non-unique
secondary index column of the second table.
rule Rules are the name given to the method used by Teradata DWM to define what requests
are prohibited from being immediately executed on the Teradata Database. That is, the rules
enforced by Teradata DWM provide the Query Management capabilities.
S
scheduled requests The capability to store scripts of SQL requests and execute them at a
scheduled time in the future.
self-contained statement A query request that stores the result data that it generates, if any.
For example, an INSERT ... SELECT statement would be self-contained, whereas a SELECT
statement would not.
SQL Structured Query Language. An industry-standard language for creating, updating
and, querying relational database management systems. SQL was developed by IBM in the
1970s. It is the de facto standard as well as being an ISO and ANSI standard. It is often
embedded in general purpose programming languages. Programming language used to
communicate with the Teradata Database.
T
TDWM The database shared by Teradata Dynamic Workload Manager and Teradata Query
Scheduler. Previously called the dbqrymgr database.
Teradata DWM Teradata Dynamic Workload Manager. A Teradata tool used to create and
manage rules that manage access to a Teradata Database.
Teradata QS
70
Glossary
TTU Teradata Tools and Utilities. A group of products designed to work with the Teradata
Database.
W
workgroups Workgroups represent collections of related scheduled request work for users,
user groups, or accounts. Each workgroup is assigned a maximum number of requests that
can be executing from that workgroup simultaneously thereby ensuring that requests for all
workgroups get a fair share of their scheduled work done within the execution time frames.
71
Glossary
72
Index
A
Abort Job command 27, 58
aborting jobs 58
About Teradata QS Administrator command 28
About Teradata QS Administrator dialog box 28
accounts
profiles 44, 64
scheduled requests 44
workgroups 40
Allowed Results Type list 48
Allowed Scheduling list 46
Append user name check box 48
architecture, client/server 15
C
Cancel Job command 27, 57
canceling jobs 57
changing
execute time for job 55
scheduler profiles 45
workgroups 41
cleaning up, scheduler profiles 50
client software
optional 22
required 21
CLIv2
defining the system address 22
verifying connection 22
commands See specific command names
Configuration menu 26
configuring scheduled requests 37
copyright information, viewing 28
Create as Fallback check box 48
Create as Multiset check box 48
creating
execution time frames 38, 39
results file storage locations 44
scheduler profiles 45
workgroups 40, 41
D
Database Name box 36
database name, specifying 22
database requirements 22
DB Date 30
DB Time 30
Delete Job command 27, 57
Delete Request command 27, 56
deleting
execution time frames 40
inactive Teradata QS Server 38
jobs 57
scheduled requests 56
scheduler profiles 50
workgroups 42
dialog box help, viewing 20
dialog boxes See specific dialog box name
Disable Scheduling command 26
disabling scheduled requests 37, 46
dispatching jobs 18
drivers
ODBC 22
TCP/IP 21
Token Ring packet 21
Drop Results command 27, 58
dropping results 58
E
Edit Results File Storage dialog box 63
editing
execution time frames 39
results file storage locations 43
scheduler profiles 45
workgroups 41
e-mail notifications, setting up 59
Enable Scheduling command 26
Enable Time Frame check box 39
enabling scheduled requests 37
Everyday check box 40
Execute Now command 27, 56
executing jobs 18
execution time frames
creating 39
deleting 40
editing 39
Execution Time Frames command 26
Execution Time Frames dialog box 39, 40
Exit command 26
exiting Teradata QS Administrator 37
73
Index
F
Field Separator Character list 48
File menu 26
file storage locations See results file storage locations
file storage See results file storage
Font command 28
G
glossary 67
H
Help menu 28
Help Topics command 28
help, opening online 20
HOSTS file, modifying 22
I
Information column 29, 53
Interval command 28
IP address, specifying 22
N
Name box 46
network connection, verifying 22
New Results File Storage dialog box 63
Next Execute Time 30
notifications, setting up e-mail 59
Now command 27
O
online help, opening 20
operating systems, supported 21
Optional Sub-Directory box 48
Options menu 27
overviews
results file storage 42
scheduled requests 17
scheduler profiles 44
Teradata QS interfaces 25
Refresh command 27
Refresh Interval dialog box 54, 61
refresh rate, setting 54
rejected requests, scheduling 59
Request ID column 29, 53
Request Name column 29, 53
requests See scheduled requests
results
automatic cleanup of data tables 45
database table, saving to 43
dropping 58
Results Database box 48
Results Duration box 45, 48
results file storage
creating 42
managing
TDWM database 31
Teradata QS database 31
Max File Size box 48
Mechanism list box 36
menu bar 25
migrating
Teradata QS database 32
Modify create Table as Fallback option check box 49
Modify create Table as Multiset option check box 49
Modify Execute Time command 27
Modify Field Separator Char check box 49
Modify Maximum Start Interval check box 49
74
Parameter box 36
Password box 36
platforms, supported 3
product release numbers 3
Profile Type box 46
profiles See scheduler profiles
Q
Query Scheduler Server Status window 38
Index
designating 42
overview 42
Results File Storage box 44
Results File Storage command 26
Results File Storage dialog box 43, 44, 62
Results File Storage list 48, 62
results file storage locations
creating 44
deleting 44
editing 43
Results File Storage Properties dialog box 44, 63
Results Tables/Files tab 47
S
Scheduled column 29, 53
Scheduled Profile Properties dialog box 45
scheduled requests
checking 18
configuring 37
deleting 56
disabling 37
enabling 37
overview 17
profiles See scheduler profiles
results
saving in a shared network directory 43
saving into files 43
scheduling rejected 59
SQL statements, viewing 55
time frames See execution time frames
viewing 53
Scheduled Requests list 25
columns, sorting 29
refresh rate, setting 54
Teradata QS Administrator 28
scheduler profiles
cleaning up 50
creating 45
deleting 50
modifying 45
overview 44
Scheduler Profiles command 26
Scheduler Profiles dialog box 45, 50, 64
Scheduling tab 46
Server Status command 27
Servers menu 27
Session Character Set list box 36
setting
execution time frames for scheduled requests 38
refresh rate, Scheduled Requests list 54
shortcut menu 29
Show SQL command 27, 55
software releases, supported 3
T
TCP/IP driver 21
TDWM database
managing 31
Teradata QS
view-only mode, opening in 36
Teradata QS Administrator
commands 25
exiting 37
Scheduled Requests list 28
shortcut menu 29
starting 35
status bar 25, 30
Teradata QS database
managing 31
migrating 32
Teradata QS Server
inactive server, deleting 38
starting 20
status, viewing 38
Teradata Query Scheduler Admin Logon dialog box 36
Teradata Query Scheduler Operations utility 16
Teradata Query Scheduler Viewer 16
Teradata SQL Assistant
client software, installing 22
rejected requests, scheduling 59
Time Frame Properties dialog box 39
time frames See execution time frames
U
Use Data Encryption check box 36
User Name box 36
User Name column 29, 53
User Options tab 49
user profiles, scheduled requests 44
users, scheduler profiles 44
V
version numbers
Teradata Database 3
Teradata QS Administrator 28
75
Index
W
Windows Results Directory box 44
Workgroup list 46
Workgroup Properties dialog box 41, 66
workgroups
creating 40, 41
deleting 42
editing 40, 41
Workgroups command 26
Workgroups dialog box 41, 42, 65
76