Defining a Workload From QCD Statements - Teradata Index Wizard

Teradata Index Wizard User Guide

Product
Teradata Index Wizard
Release Number
15.00
Language
English (United States)
Last Update
2018-09-28
dita:id
B035-2506
lifecycle
previous
Product Category
Teradata Tools and Utilities

Defining a Workload From QCD Statements

SQL statements can be selected from the query capture database (QCD). Use this option if the execution plans are already available in the QCD.

The Query ID and the Query Tag fields are optional. If no values are entered in these fields, all the statements in the QCD are displayed when you click the Browse button.

Query IDs can be added as individual queries separated by comma(s). For example: 1, 2, 3. Use hyphens to separate queries in a range. For example: 5-10. Commas and hyphens can be used together. For example: 1, 2, 3, 5-10.

The Query Tag field is used to retrieve statements from the QCD. The field also accepts wild card characters. Using a percentage sign (%) in this field, loads all the queries from the specified database.

To define a workload from the QCD

1 Click Workload > Create > From QCD Statements.

The Define Workload from QCD Statements dialog box opens.

2 Fill in the dialog box to set the criteria for defining the workload.

The following table describes the options in this dialog box.

 

Option

Description

QCD Name

Enter the QCD name to be browsed for SQL statements or click .

Query ID

Enter the Query ID of the statements.

Query Tag

Enter the Query Tag of the statements.

Browse QCD

Searches the QCD for statements based on the Query ID, or Query Tag values entered.

Workload Name

Creates a workload with the “workloadname” description for the selected statements in the grid.

Select All

Selects all the statements in the list.

Deselect All

Deselects all the statements from the list.

3 Click OK to start the workload definition process.

When the process is complete, the Workload Definition Summary window opens.

4 Check the workload, and click OK.

The workload is now in the workload cache and is ready to be analyzed. For more information, see “Chapter 6 Analysis” on page 81