July 2019 |
7.5 |
- Updated product name from Teradata Vantage for Azure to Teradata Vantage on Azure (run-it-yourself).
- Removed L8S and L32S from Supported Database VM Sizes table.
- Added the procedure for upgrading the Teradata Database or NewSQL Engine operating system and removed other upgrading procedures.
- Removed the Backing Down Teradata Software for Azure section.
- Updated the Supported Versions topic.
- Removed listing of China in Special Regions.
- Updated links to run-it-yourself information on the Teradata website.
- Added the Adding Azure Blob Storage topic.
- Updated the Fallback section as users can no longer disable fallback.
- Removed outdated entitlement management information and updated BYOL information to reflect annual licenses and private offers.
- Added Supported Database Disk Sizes topic.
- Updated references of Teradata Database to Teradata Vantage.
|
January 2019 |
6.02 |
- Added support for Teradata Unity.
|
November 2018 |
6.0 |
- Added support for scaling out and scaling in incrementally.
- Added support for hot standby nodes for node failure recovery.
- Added Storage Size Per Node (in TB) to the ecosystem solution template to choose additional storage options at deployment.
- Added support for Dsv3- and Esv3-series VM sizes for network-attached SSD storage.
- Added support for D15_v2, L8S, and L32S VM sizes for VM-resident SSD storage.
- Added support to convert existing VMs running on three NICs to run on one NIC.
- Added support for renewing a license for BYOL.
- Added hourly support for, and removed BYOL from, US Government regions.
- Added support for Teradata Database 16.20 Feature Update 1. Removed support for Teradata Database 15.10.
- Updated references to product offerings in the Azure Marketplace from Teradata Database to Teradata Vantage.
- Replaced Teradata Support with Teradata Customer Portal.
- Replaced Teradata REST Services with Teradata Query Service.
- Changed solution template parameter from Fold/Unfold to Scale Out/In and command names for scaling out and scaling in after deployment.
|