NORMALIZE specifies that period values in the first period column that meet or overlap are combined to form a period that encompasses the individual period values.
|
Syntax Element … |
Specifies … |
|
NORMALIZE |
that the result of the select is normalized on the first period column in the select list. Period values that meet or overlap are coalesced, that is, combined to form a period that encompasses the individual period values. Any period columns that are specified after the first period column are treated as regular column values. Normalize is the last operation performed on the result of a SELECT statement. You can use a SELECT statement with the normalize clause on a normalized or non-normalized table. A SELECT statement cannot normalize a derived period column. |
|
ON MEETS OR OVERLAPS |
period values that meet or overlap are to be coalesced, that is, combined to form a period that encompasses the individual period values. |
|
ON OVERLAPS |
period values that overlap are to be coalesced, that is, combined to form a period that encompasses the individual period values. |
|
ON OVERLAPS OR MEETS |
period values that overlap or meet are to be coalesced, that is, combined to form a period that encompasses the individual period values. |
|
table_name |
the name of a table for which all the attributes of all its structured UDT columns are to be returned. |
|
column_name |
the name of a column in the named query definition. You can specify a row‑level table constraint column in the select list of a SELECT statement, as long as it is not part of an arithmetic expression. The value returned for the column is the coded value for the row-level security constraint from the row. Colu4mns with a UDT type are valid with some exceptions. See “Specifying UDTs in an SQL Request” on page 19 for the specific exceptions. You cannot specify LOB columns with NORMALIZE. |
NORMALIZE is aTeradata extension to the ANSI SQL:2011 SQL standard.