Usage Notes - Advanced SQL Engine - Teradata Database

Data Dictionary

Product
Advanced SQL Engine
Teradata Database
Release Number
17.05
Published
January 2021
Language
English (United States)
Last Update
2021-01-22
dita:mapPath
prb1610499325399.ditamap
dita:ditavalPath
hoy1596145193032.ditaval
dita:id
B035-1092
lifecycle
previous
Product Category
Teradata Vantageā„¢

QryLogFeatureUseCountV provides use counts based on the current data in DBC.DBQLogTbl.

The QryLogFeatureUseCountV view is populated if the WITH FEATUREINFO option for BEGIN/REPLACE QUERY LOGGING and this view (QryLogFeatureUseCountV) is included in a request. QryLogFeatureUseCountV provides a view into the FeatureUsage column of DBQLogTbl and the QryLogFeatureListV view.

Specific and Generic Feature Names

The feature list includes specific feature names and, in certain cases, generic feature names. The generic feature name is logged when any of the corresponding specific feature names is logged. Not all specific features have a corresponding generic feature group. The following table is a partial list of specific feature names with corresponding generic feature names.
The list below is provided as an example of specific and generic feature grouping, but is not a complete list of features. The features list and the grouping of features is subject to change.
Specific Feature Name Generic Feature Name
24 Teradata Columnar 109 Column Partitioning
27 Multi Level Partitioning 26 Row Partitioning
28 8 Byte Partitioning
29 2 Byte Partitioning
30 Column Partitioning and Row Partitioning 26 Row Partitioning, 109 Column Partitioning
31 Column-Partitioned and a NoPI 109 Column Partitioning
32 Column-Partitioned and a PI
33 Column-Partitioned and a PA
42 XML Data Type 41 User Defined Type
43 JSON Data Type
44 Distinct Data Type
45 Structure Data Type
46 Geospatial
47 3D Geospatial
48 Period Data Type
49 Array Data Type
50 Number Data Type
104 Aggregation Push for Union All 110 Union All Pushdown
105 Binary Join Push for Union All

Example: Using QryLogFeatureUseCountV

The example generates a report on feature usage.

SELECT cast(featurename as CHAR(50)) as FEATURENAME, FEATUREUSECOUNT 
FROM DBC.QryLogFeatureUseCountV order by 2 desc;

Result:

FEATURENAME                       FEATUREUSECOUNT
--------------------------------  ---------------
Block Level Compression                      8371
Primary Index                                8371
Hashed Table                                 8371
SET Table                                    7366
Non Unique Hashed Index                      6018
Fallback                                     3298
Unique Hashed Index                          3016
Parameterized Query                          1911
Partition Level Locking                      1659
Secondary Index                              1230
Teradata Stored Procedure                    1174
[...]
Autoreparse                                    15
User Defined Function                          11
Join Index                                      8
Bit Manipulation Function                       5
Fast Path Function                              5
MloadX                                          0
[...]