Supported Database VM Sizes | Teradata VantageCloud Enterprise on Azure (DIY) - Supported Database VM Sizes - Teradata® VantageCloud Enterprise on Azure

VantageCloud Enterprise on Azure (DIY) Installation and Administration Guide - 3.2.0.0
Deployment
VantageCloud
Edition
Enterprise
Product
Teradata® VantageCloud Enterprise on Azure
Release Number
3.2.0.0
Published
March 2026
ft:locale
en-US
ft:lastEdition
2026-04-07
dita:mapPath
cvo1751050001343.ditamap
dita:ditavalPath
kou1751058502043.ditaval
dita:id
eqk1475705518038
Product Category
Cloud

The following table lists supported database VM sizes.

Storage VM Size vCPU Count Memory (GiB) Throughput (MBps) TCore License Tier*
Network- attached SSDv1 + SSDv2 E8sv5 8 64 290 1.46 B, A, E
E16sv5 16 128 600 2.97 B, A, E
E32sv5 32 256 865 5.18 B, A, E
E48sv5 48 384 1315 7.81 B, A, E
E64sv5 64 512 1735 10.37 B, A, E
E96sv5 96 672 2600 15.54 B, A, E
E104isv5 104 672 4000 19.54 B, A, E
E48dsv5 (only ssdv2) 48 384 1315 8.59 B, A, E
*B/Base, A/Advanced, E/Enterprise

Supported Clique Sizes (Esv5 with Multi-Node Clique)

On VantageCloud Enterprise 3.2 release, all the new deployments continue to use multi-node clique (MNC) architecture. The MNC is a high-availability architecture where all compute nodes share the same storage disks and is enabled on Azure using Microsoft’s shared disk capability. The advantage of this architecture is, if a node fails, a Hot Standby Node (HSN) can take over and thus minimizes the downtime.

With the addition for support of new instance types and Premium V2 LRS disks, the following table summarizes the supported clique sizes for 3.2:

Storage Storage Type Clique Size
E8sv5 SSDv2 3+1
E16sv5 SSDv2 7+1
E32sv5 SSDv2 7+1
E48sv5 SSDv2 7+1
E64sv5 SSDv2 7+1
E96sv5 SSDv2 7+1
E104isv5 SSDv2 7+1
E48dsv5 SSDv2 7+1
E8sv5 SSDv1 2+1
E16sv5 SSDv1 2+1
E32sv5 SSDv1 2+1
E48sv5 SSDv1 2+1
E64sv5 SSDv1 2+1
E96sv5 tier 3 SSDv1 2+1
E104isv5 tier 1 SSDv1 4+1

The following table is an example of the configuration for different instance sizes and disk combinations.

Storage Storage Type Clique Size Node count Clique size Total Nodes deployed[SG1]
E8sv5 SSDv2 3+1 3 1*(3+1) 4
E16sv5 SSDv2 7+1 10 1*(7+1)+1*(3+1) 12
E8sv5 SSDv1 2+1 3 1*(2+1)+1*(1+1) 5
E96sv5 tier 3 SSDv1 2+1 2 1*(2+1) 3
E104isv5 tier 1 SSDv1 4+1 12 3*(4+1) 15
Usage of HSN will incur additional infrastructure costs but does not affect your software licensing costs. You can plan accordingly.

Variable AMP Feature

This feature provides flexibility for selecting AMPs per Sub-pool and Sub-pools per node for supported instances.

While deploying the site, the Azure portal has the validations in place for Sub-pools per node and it’s relative value for AMPs per sub-pool for each instance type. The formula to calculate AMPs is:

AMPs per clique (or) AMPs per node = (AMPs per subpool) * (subpools per clique (or) subpools per node)

The following table lists the AMPs from 4 to 32 for v5.

SKU FSG Cache% Subpools Per Node (INPUT) 1
AMPs Per Subpool (INPUT) 4 6 8 10 12 14 16 18 20 22 24 26 28 30 32
APN Per SKU (Below)
Standard_E8_v5 65   4 6 8 10 12                    
Standard_E16s_v5 80   4 6 8 10 12 14 16 18 20 22 24        
Standard_E32s_v5 85   4 6 8 10 12 14 16 18 20 22 24 26 28 30 32
Standard_E48s_v5 85     6 8 10 12 14 16 18 20 22 24 26 28 30 32
Standard_E64s_v5 85           12 14 16 18 20 22 24 26 28 30 32
Standard_E96s_v5 85                 18 20 22 24 26 28 30 32
Standard_E104is_v5 85                       24 26 28 30 32
Standard_E48ds_v5 30     6 8 10 12 14 16 18 20 22 24 26 28 30 32

The following table lists the AMPs from 34 to 62 for v5.

                                     
SKU FSG Cache % Subpools Per Node (Input) 1
AMPs per Subpool (Input) 34 36 38 40 42 44 46 48 50 52 54 56 58 60 62 64
APN Per SKU (Below)
Standard_E8_v5 65                                  
Standard_E16s_v5 80                                  
Standard_E32s_v5 85   34 36 38 40 42 44 46 48                
Standard_E48s_v5 85   34 36 38 40 42 44 46 48 50 52 54 56        
Standard_E64s_v5 85   34 36 38 40 42 44 46 48 50 52 54 56 58 60 62 64
Standard_E96s_v5 85   34 36 38 40 42 44 46 48 50 52 54 56 58 60 62 64
Standard_E104is_v5 85   34 36 38 40 42 44 46 48 50 52 54 56 58 60 62 64
Standard_ E48ds_v5 85   34 36 38 40 42 44 46 48 50 52 54 56        
You cannot change the number of AMPs per node after deploying the DIY stack.

Deploying a Software Ecosystem

For provisioning and deployment requests, reach out to Teradata Sales/Account teams.

Related information