16.20 - BLOCKCOMPRESSION - Teradata Database - Teradata Vantage NewSQL Engine

Teradata Vantage™ SQL Data Definition Language Syntax and Examples

Product
Teradata Database
Teradata Vantage NewSQL Engine
Release Number
16.20
Published
March 2019
Language
English (United States)
Last Update
2019-05-24
dita:mapPath
wkf1512081455740.ditamap
dita:ditavalPath
TD_DBS_16_20_Update1.ditaval

Specifies whether the data in the hash index should be block-compressed based on the temperature of the cylinders on which it is stored.

You can specify the following settings for block_compression_option.

AUTOTEMP
The compressed state of the data in the hash index can be changed by Teradata Database at any time based on its temperature.
You can still issue query band options or Ferret commands, but if the compressed state of the data does not match its temperature, such changes might be undone by the system over time.
DEFAULT
The hash index uses the compression option (MANUAL, AUTOTEMP or NEVER) set in the DBS Control parameter DefaultTableMode. For details, see Teradata Vantage™ - Database Utilities , B035-1102 . Note that value of DefaultTableMode is not saved in the hash index definition as part of a CREATE HASH INDEX request, so a hash index set to DEFAULT is affected by any future change to the DefaultTableMode parameter.
MANUAL
That block level compression is applied based on the default for the hash index at the time the hash index is created. Hash indexes can be compressed or uncompressed at any time after loading by using the Ferret COMPRESS and UNCOMPRESS commands. Data inserted into the existing hash index inherits the current compression status of the hash index at the time the data is inserted.
NEVER
The hash index is not compressed even if the DBS Control block compression settings indicate otherwise. Teradata Database rejects Ferret commands to manually compress the hash index, but Ferret commands to decompress the index are valid.