6.02 - Azure Service Limits - Teradata Software for Azure

Teradata® Software for Azure Installation and Administration Guide

prodname
Teradata Software for Azure
vrm_release
6.02
category
Administration
Configuration
Installation
featnum
B035-2810-128K

When you create your Azure account, Azure sets default service limits on certain resources on a per-region basis. Before deploying VMs, check the limits to determine if any should be increased especially for core, networking, and storage. Plan to request limit increases before you need them.

To request limit increases, create an Azure support request. When you create a support request, select the issue type (always Quota), your subscription, support plan, severity, deployment model (Resource Manager), location (region), and specify VMs that apply to this request. The table below lists some request types for which you might need to increase service limits.

Before using DSU, check the maximum Azure storage account capacity. For more information on Azure storage account limits and performance targets, see Azure Documentation Center.

Before scaling out a system, you might need to increase Azure service limits, which cannot be automatically detected before you scale out. Since scaling out requires additional resources like VMs, NICs, and managed disks, make sure there are sufficient resources in your resource group.

Request Type Quota Type Details
Cores Compute (cores/vCPUs) Request the number of additional cores, including if you plan to scale out a system.
Networking Limits Networking: ARM Request the number of additional public IPs, specify the region where they are needed, and provide a detailed justification.

Before deploying a Teradata Database MPP image, increase the public IP limits to sufficiently meet your needs.

Storage Storage: ARM Request the number of additional premium storage accounts and specify the region where they are needed.