Considerations and Limitations - Teradata Software for Azure

Teradata Vantageā„¢ on Azure (DIY) Installation and Administration Guide

Product
Teradata Vantage on Azure
Release Number
5.01
Published
July 2018
Language
English (United States)
Last Update
2018-07-18
dita:mapPath
kmk1523992471627.ditamap
dita:ditavalPath
TeradataAzure_PubCloud_5.01_5.01.01.ditaval
dita:id
B035-2810
lifecycle
previous
Product Category
Cloud

Consider the following limitations before scaling out or scaling in.

Considerations Limitations
Database license tier Developer tier is not supported.
Maximum node limit Do not scale out the system beyond the maximum node limit.

For BYOL, make sure you have enough TCores before you scale out the system.

Maximum data disk count per node limit Do not scale in the system if it increases the volume count beyond 32 for DS14_v2 and 40 for DS15_v2.
Maximum scale out limit Do not scale out the system beyond the maximum node count limit. You cannot go beyond the minimum storage subpool count of 1 per node.

Do not scale out beyond four times (4x) the size of a launched 16 or 20 AMPs per node system.

Minimum scale in limit Do not scale in the system beyond the maximum storage subpool count of 4 per node.
Power of two scaling limit A system can be scaled out to only two times (2x) the size, which doubles the total node count (half the premium storage), or four times (4x) the size, which quadruples the total node count (quarter the premium storage).

Assuming a system was previously scaled out, it can be scaled in only two times (2x, scale factor x/2) or four times (4x, scale factor x/4).