Post Processing

Teradata Warehouse Miner User Guide - Volume 1Introduction and Profiling

Teradata Warehouse Miner
User Guide
None of the fields on this screen except Further SQL Commands to Execute is enabled when connected to an Aster database.

The post processing tab is available for most analyses that produce an output table or view. The panel shown below is given if output is directed to a database table. If it is directed to a database view, then only the first option is provided, with the label changed to Comment on Output View. In general, Collect Statistics and Further SQL commands are applied to both permanent and volatile tables with exceptions noted below, while Comments are ignored for volatile tables.

  • The Variable Transformation analysis does not collect statistics for the volatile table created when null value replacement is performed in combination with a specific transformation.
  • The Data Explorer analysis can produce multiple output tables, and so applies the requested post processing equally to each of the output tables, but notably does not offer the Further SQL commands to execute option.
  • The Sample analysis can produce a table, multiple tables or a table plus multiple views, and so applies the requested post processing to each output table or view as appropriate. In particular, the Comment on Output Table option is applied to each permanent table and view, while the Collect Statistics command is applied to both volatile and permanent tables and Further SQL commands options are applied only to permanent output tables.
    The Sample analysis is only available when connected to a Teradata database.
    Output Post Processing on Teradata Database

The following options are available only when connected to a Teradata database:
  • Comment on Output Table — Enter a comment without quotes (up to 255 characters) to be applied to the output table or view via an SQL COMMENT statement. It may contain substitution parameters for the output category (Score, ADS, Stats or Other), project name and/or analysis name (using the tags <Category>, <Project> and <Analysis>, respectively).

    Note that the default value of this field may be set on the Defaults tab of the Preferences dialog box that is available from the Tools > Preferences menu option.

    This field is ignored for volatile tables.

  • Collect Statistics on Primary Index of Output Table — Option to collect statistics on the primary index of the output table via an SQL COLLECT STATISTICS statement. This request is performed for both permanent and volatile tables except as already noted.
    • Use a Sample in collecting the statistics — Option to specify that a system-selected percentage of rows be used in collecting the statistics rather than performing a full-table scan.
  • Further SQL commands to execute — Free-form SQL commands can be entered here to be executed against the output table during post-processing. It is important to substitute the symbols <T> in place of the name of the output table in these commands so that if the output table or database changes in this analysis, in a Refresh analysis or in the Model Manager web-based application, the correct output table name will be in force. This request is performed for both permanent and volatile tables except as already noted.
    If stored procedure output is requested for the analysis or for a Refresh chained to the analysis, the last SQL command must be terminated by a semi-colon.