[Base, Advanced, and Enterprise tiers only] You can add or remove nodes from an existing system. Adding nodes is referred to as scale out. Removing nodes is referred to as scale in. Scale out and scale in supports only premium storage. A system can always be scaled in after it is scaled out.
- Increases the system performance by adding more CPU and memory, and increases the storage bandwidth by decreasing the data disks managed per node.
- Increases the node count by provisioning additional VMs and other resources causing an increase in infrastructure and software costs.
- Consumes additional subnet space. The subnet must have enough IP addresses for the new VMs being added to the system.
- Migrates the premium data disks from existing to new VMs.
- Decreases the system performance by removing CPU and memory, and decreases the storage bandwidth by increasing the data disks managed per node.
- Decreases the node count by terminating VMs that are no longer needed and associated resources causing a decrease in infrastructure and software costs.
- Migrates the premium data disks from the nodes that are removed to the remaining nodes.
The database capacity and AMP count does not change. When scaling out and scaling in, the number of AMPs gets redistributed evenly across the nodes.
If either scale out or scale in cannot complete successfully, the process automatically attempts to roll back the operation and restore the original configuration. If rollback fails, contact Teradata Customer Support.
To scale out or scale in, see the following instructions. Before scaling out or scaling in, you may need to increase Azure service limits.
| Action | Instructions |
|---|---|
| To scale out at deployment | Deploying a Teradata Software Ecosystem from a Solution Template |
| To scale in at deployment | You cannot scale in at deployment, only after deployment. |
| To scale out after deployment | Scaling Out a System |
| To scale in after deployment | Scaling In a System |