Importing a Workload - Teradata Index Wizard

Teradata Index Wizard User Guide

Product
Teradata Index Wizard
Release Number
15.10
Language
English (United States)
Last Update
2018-10-07
dita:id
B035-2506
Product Category
Teradata Tools and Utilities

SQL statements can be imported from another system onto a test system. When the file containing the imported workload information (.mcf file) is opened, the environment of the production system is imported onto the test system.

1 Click Workload>Create> Import Workload

The Select a File to Import Workload dialog box opens.

2 Choose the workload file to import, and click Open.

The Import File dialog box opens with the workload you selected.

3 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

Import Into

Parent Database

Selects the parent Teradata Database that you will be importing information into.

Target QCD Name

Enter or use the Browse (...) button to select the QCD Name under which the imported workload is stored.

Select

QCD Name

Select the QCD name from the imported workload.

Workload Name

Select the name of workload to be imported.

Import Options

Check Boxes>

Object definitions
Statistics
Random AMP Sample
Demographics
Execution Plan
Workloads
QCD Data
Cost Parameters
Cost Profiles

Use these check boxes to set import options for the workload you are importing. See “Import Options” on page 68 for a detailed explanation of these options.

Import

Starts the import operation.

Set TLE

Opens the Set Target Emulation dialog box. For more information, see “Setting the TLE” on page 64.

Error Handling

Opens the Error Handling dialog box, which has several options for handling errors that may occur when importing a workload. For more information, see “Handling Errors” on page 66.

4 Click Import to start the workload definition process.

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

5 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.