Macro Support for Large Objects - Analytics Database - Teradata Vantage

SQL Data Definition Language Detailed Topics

Deployment
VantageCloud
VantageCore
Edition
Enterprise
IntelliFlex
VMware
Product
Analytics Database
Teradata Vantage
Release Number
17.20
Published
June 2022
Language
English (United States)
Last Update
2023-07-11
dita:mapPath
vuk1628111288877.ditamap
dita:ditavalPath
qkf1628213546010.ditaval
dita:id
B035-1184
lifecycle
latest
Product Category
Teradata Vantage™

You can use BLOB and CLOB columns in macros as long as they do not violate the restrictions on large object use with SQL.

These restrictions are named in the following bulleted list:
  • You cannot create a base table with more than 32 LOB columns, nor can you alter a base table to have more than 32 LOB columns.
  • You can increase the maximum size of a LOB column up to the system limit, but you cannot decrease the maximum size of an existing LOB column.
  • LOB columns can only carry the following attributes:
    • NULL
    • NOT NULL
    • TITLE
    • FORMAT
  • LOB columns cannot be a component of any index.
  • A base table containing LOB columns must have at least one non-LOB column to act as its primary index.
  • The first column specified in a base table definition cannot be a LOB unless a uniqueness constraint is defined on some non-LOB column set in that table.
  • The uniqueness of a SET base table must be defined on the basis its non-LOB column set because LOB columns cannot be used to specify row uniqueness.
  • You cannot define integrity constraints on LOB columns, nor can you define integrity constraints that reference LOB columns.
  • LOB columns can be components of a view subject to the restrictions provided in this list and the semantics of view definitions.
  • LOB columns can be parameters of a user-defined function.

For more information, see Teradata Vantage™ - Data Types and Literals, B035-1143.