A cylinder can have only one of the space type (Perm/Spool/Temp)
Datablock can have rows from only one table
Cylinder can have rows from multiple tables.
Adavanced Format Drives have native sector size of 4K. DB Size automatically adjusted to be even multiples of 4KB
On cylinder full condition, following alternatives are considered
Cylinder migrate to adjacent cylinder: max of 10 blocks are moved
Cylinder migrate to a new: Max of 10 blocks are moved
During cylinder migration,
they are defragmented in background if they have >= 25% free space
if number of free cylinders fall below 10, mini cylpack to free up a cylinder
mini cylpack never happens on spool space
AutoCylPack runs in background when system is idle. Merge up to 8 small blocks (<MergeBlockRatio) within a single cylinder during FTS update scans (no empty INS-SEL)
specified at CREATE TABLE, DBSControl FREESPACEPERCENT, FERRET PACKDISK
honored during: FLOAD, MLOAD (empty), INS-SEL (empty), CREATE SI
ignored during: mini cylpack, all other data load ops except above
online reconfig: Allows adding new nodes while system is up
Uses ReconfigRedistOrderTbl and ReconfigDeleteOrderTbl system tables
ROT Larger (1MB) block size:
Use 512KB on appliance, 256K on EDW, 1MB for spool
For OLTP applications, do not use large block size
Rows in big blocks are aligned on 4 byte v/s 2 byte => increase in tablesize
Intermediate spool DB and row size can be up to 1MB; but final spool size is limited to 64K
Big blocks require more memory to hold block. As a consequence, when doing multicontext operations such as sliding window merge join or columnar inserts may be slower.
DBC tables, JI and HI can’t specify DB size but use the default value
Base TVS (included in all versions of Teradata, paid or not), has two basic functions:
Pool all cylinders within the clique and allocate to AMPs (instead of entire PDISK)
Due to this, a single disk failure can affect multiple AMPs. Hence, Intelliflex systems require FALLBACK
Count accesses to the cylinders to understand the usage patterns (temperature)
TVS
Can operate in Traditional (compatibility) or Intelligent Placement modes
Allocates 20% of fast storage to WAL and spool. These cannot cool off
TVS designated VERY HOT data is kept in TIM by PDE
VH Cache data is brought back into memory after restart
Storage can be plugged into IFX in units that are not multiples of the number of AMPs (eg 20 AMPs on a node does not require 20 storage units to be added). TVS carves that up and hands out the cylinders to the AMPs. This makes storage addition much more flexible.
TIM. The usage pattern information is key to implementing TIM. Without it we do not know what to put/keep in TIM memory.
TBBLC. Temperature based compression depends on the usage information as well. In this case we care about the low usage data versus TIM wanting to identify the high usage data.