The following table lists supported database VM sizes. For information on supported configurations, see https://www.teradata.com/Cloud/Azure/Do-it-Yourself/Pricing.
Storage | VM Size | vCPU Count | Memory (GiB) | Throughput (MBps) | TCore | License Tier* |
---|---|---|---|---|---|---|
Network-attached SSD | E16s_v4 | 16 | 128 | 384 | 2.48 | B, A, E |
E32s_v4 | 32 | 256 | 768 | 4.96 | B, A, E | |
E32-16s_v4 | 16 | 256 | 768 | 3.36 | B, A, E | |
E32-8s_v4 | 8 | 256 | 768 | 2.56 | B, A, E | |
E64s_v4 | 64 | 432 | 1200 | 9.14 | B, A, E | |
E64-32s_v4 | 32 | 432 | 1200 | 5.94 | B, A, E | |
E64-16s_v4 | 16 | 432 | 1200 | 4.34 | B, A, E | |
VM-resident SSD | D15_v2 | 20 | 140 | 894 | 6.04 | D |
*D/Developer, B/Base, A/Advanced, E/Enterprise |
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)SKU | FSG Cache (%) | Subpools Per Node (INPUT) | 2 | 4 | 8 | |||||||||
AMPs Per Subpool (INPUT) | 3 | 4 | 5 | 6 | 3 | 4 | 5 | 6 | 3 | 4 | 5 | 6 | ||
APN Per SKU (Below) | ||||||||||||||
Standard_E16s_v4 | 80 | 6 | 8 | 10 | 12 | N/A | 16 | 20 | 24 | N/A | N/A | N/A | N/A | |
Standard_E32s_v4 | 85 | 6 | 8 | 10 | N/A | 12 | 16 | 20 | 24 | N/A | 32 | 40 | 48 | |
Standard_E32-16s_v4 | 85 | 6 | 8 | 10 | N/A | 12 | 16 | 20 | 24 | N/A | 32 | 40 | 48 | |
Standard_E32-8s_v4 | 85 | 6 | 8 | 10 | N/A | 12 | 16 | 20 | 24 | N/A | 32 | 40 | 48 | |
Standard_E64s_v4 | 85 | N/A | N/A | N/A | N/A | 12 | 16 | 20 | N/A | 24 | 32 | 40 | 48 | |
Standard_E64-32s_v4 | 85 | N/A | N/A | N/A | N/A | 12 | 16 | 20 | N/A | 24 | 32 | 40 | 48 | |
Standard_E64-16s_v4 | 85 | N/A | N/A | N/A | N/A | 12 | 16 | 20 | N/A | 24 | 32 | 40 | 48 |
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.