Skip to content

Commit fbb4235

Browse files
authored
Minor edit
1 parent 1db8be9 commit fbb4235

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

articles/sap/workloads/dbms-guide-sqlserver.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -139,7 +139,7 @@ If the result is different, STOP any deployment and investigate why the setup co
139139
Using SQL Server in Azure IaaS deployments for SAP, you have several different possibilities to add to deploy the database layer highly available. Azure provides different up-time SLAs for a single VM using:
140140

141141
* Different Azure block storages
142-
* A pair of VMs deployed in an Azure availability set
142+
* A pair of VMs deployed in an Azure Availability Set
143143
* A pair of VMs deployed across Azure Availability Zones
144144

145145
For production systems, we expect you to deploy a pair of VMs within a virtual machine scale set with flexible orchestration across two availability zones. To learn more, see [comparison of different deployment types for SAP workload](./sap-high-availability-architecture-scenarios.md#comparison-of-different-deployment-types-for-sap-workload). One VM runs the active SQL Server Instance. The other VM runs the passive instance.

0 commit comments

Comments
 (0)