architecture-center
architecture-center copied to clipboard
MicrosoftDocs
SQL Server Availability Group Wording Fixes
Within this Workflow section, the following bolded words and phrases are kinda/sorta not accurate and may confuse readers:
The database tier can be configured to use Always On availability groups. With this SQL Server configuration, one primary database within a cluster is configured with up to eight secondary databases. If an issue occurs with the primary database, the cluster fails over to one of the secondary databases, allowing the application to remain available. For more information, see Overview of Always On availability groups for SQL Server.
I would suggest the following edits to reflect the concept of primary and secondary 'replicas' within an Availability Group, removing the reference to a cluster failing over given Availability Groups are not true Failover Cluster Deployments of SQL Server, and minor other edits to ensure clarity. For reference, the official listing of Availability Group terms and conditions can be found here
Proposed edits are bold and italic:
The database tier can be configured to use Always On availability groups. With this SQL Server configuration, one primary read/write replica within an availability group is configured with up to eight secondary read-only replicas. If an issue occurs with the primary replica, the availability group fails over primary read/write activity to one of the secondary replicas, allowing the application to remain available. For more information, see Overview of Always On availability groups for SQL Server.
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
- ID: 5e6bcac8-81a4-74ef-8287-6a185c564e84
- Version Independent ID: 5e6bcac8-81a4-74ef-8287-6a185c564e84
- Content: Multi-tier web application built for HA/DR - Azure Example Scenarios
- Content Source: docs/example-scenario/infrastructure/multi-tier-app-disaster-recovery-experiment.yml
- Service: architecture-center
- Sub-service: example-scenario
- GitHub Login: @sujayt
- Microsoft Alias: sutalasi
@kenjmartinii Thanks for your feedback! We will investigate and update as appropriate.
@kenjmartinii - our apologies for the long delay, and thanks very much for your contribution.
Your suggestions have been incorporated. The article will republish by around 10am Pacific on 11/21.
#please-close
