[Base, Advanced, and Enterprise tiers only] You can scale up or down and scale out or in your system after deployment using the command line.
Refer to this table to determine which option is appropriate for your use case.
| Action | Effect | Scale Up1 | Scale Down1 | Scale Out2 | Scale In2 |
|---|---|---|---|---|---|
| Decrease CPU count | Decreases performance | ● | ● | ||
| Decrease memory size | Decreases performance | ● | ● | ||
| Decrease storage bandwidth of VMs | Increases data disks managed per VM | ● | ● | ||
| Increase CPU count | Increases performance | ● | ● | ||
| Increase memory size | Increases performance | ● | ● | ||
| Increase storage bandwidth of VMs | Decreases data disks managed per VM | ● | ● | ||
| Increase VM count | Changes infrastructure and software costs | ● | |||
| Replace VMs | Redistributes premium data disks across VMs | ● | |||
|
|||||
Both scaling out and scaling in support only premium storage.
See the Orange Book, Elasticity in the Teradata® Database, TDN-0009703. To find an Orange Book, go to https://support.teradata.com, log in, and search for the book title.