AWS prescriptive-guidance documentation change
Summary
Updated title, section headers, formatting (bold to italic for step headers), fixed a Microsoft blog URL, and minor text corrections
Security assessment
Changes are primarily formatting, grammatical improvements, and URL updates. The URL fix for a Microsoft blog post is a documentation maintenance change, not related to addressing a security vulnerability. No security features or vulnerabilities are discussed.
Diff
diff --git a/prescriptive-guidance/latest/patterns/configure-read-only-routing-in-an-always-on-availability-group-in-sql-server-on-aws.md b/prescriptive-guidance/latest/patterns/configure-read-only-routing-in-an-always-on-availability-group-in-sql-server-on-aws.md index 873adac3a..797827314 100644 --- a//prescriptive-guidance/latest/patterns/configure-read-only-routing-in-an-always-on-availability-group-in-sql-server-on-aws.md +++ b//prescriptive-guidance/latest/patterns/configure-read-only-routing-in-an-always-on-availability-group-in-sql-server-on-aws.md @@ -7 +7 @@ SummaryPrerequisites and limitationsArchitectureToolsBest practicesEpicsTroubles -# Configure read-only routing in an Always On availability group in SQL Server on AWS +# Configure read-only routing in Always On availability groups in SQL Server on AWS @@ -49 +49 @@ SQL Server uses the read-only routing mechanism to redirect the incoming read-on -**Product Versions** +**Product versions** @@ -114,4 +114,4 @@ Task| Description| Skills required -Update the replicas to read-only.| To update both the primary and the secondary replica to read-only, connect to the primary replica from SSMS, and run the _Step 1_ code from the _Additional information_ section.| DBA -Create the routing URL.| To create routing URL for both replicas, run the _Step 2_ code from the _Additional information_ section. In this code, `tagechtalk.com` is the name of the AWS Managed Microsoft AD directory.| DBA -Create the routing list.| To create the routing list for both replicas, run the Step 3 code from the _Additional information_ section.| DBA -Validate the routing list.| Connect to the primary instance from SQL Server Management Studio, and run the _Step 4_ code from the _Additional information_ section to validate the routing list.| DBA +Update the replicas to read-only.| To update both the primary and the secondary replica to read-only, connect to the primary replica from SSMS, and run the _Step 1_ code from the Additional information section.| DBA +Create the routing URL.| To create routing URL for both replicas, run the _Step 2_ code from the Additional information section. In this code, `tagechtalk.com` is the name of the AWS Managed Microsoft AD directory.| DBA +Create the routing list.| To create the routing list for both replicas, run the _Step 3_ code from the Additional information section.| DBA +Validate the routing list.| Connect to the primary instance from SQL Server Management Studio, and run the _Step 4_ code from the Additional information section to validate the routing list.| DBA @@ -121 +121 @@ Task| Description| Skills required -Connect by using the ApplicationIntent parameter.| +Connect by using the `ApplicationIntent` parameter.| @@ -147 +147 @@ Task| Description| Skills required -Connect by using sqlcmd.| To connect from sqlcmd, run the _Step 5_ code from the _Additional information_ section at the command prompt. After you are connected, run the following command to show the connected server name. +Connect by using sqlcmd.| To connect from sqlcmd, run the _Step 5_ code from the Additional information section at the command prompt. After you are connected, run the following command to show the connected server name. @@ -158 +158 @@ Issue| Solution -Creating the listener fails with the message 'The WSFC cluster could not bring the Network Name resource online'.| For information, see the Microsoft blog post [Create Listener Fails with Message 'The WSFC cluster could not bring the Network Name resource online'](https://techcommunity.microsoft.com/t5/sql-server-support-blog/create-listener-fails-with-message-the-wsfc-cluster-could-not/ba-p/318235). +Creating the listener fails with the message 'The WSFC cluster could not bring the Network Name resource online'.| For information, see the Microsoft blog post [Create Listener Fails with Message 'The WSFC cluster could not bring the Network Name resource online'](https://techcommunity.microsoft.com/blog/sqlserversupport/create-listener-fails-with-message-the-wsfc-cluster-could-not-bring-the-network-/318235). @@ -172 +172 @@ Potential issues, including other listener issues or network access issues.| See -**Step 1. Update the replicas to read-only** + _Step 1. Update the replicas to read-only_ @@ -180 +180 @@ Potential issues, including other listener issues or network access issues.| See -**Step 2. Create the routing URL** + _Step 2. Create the routing URL_ @@ -188 +188 @@ Potential issues, including other listener issues or network access issues.| See -**Step 3. Create the routing list** + _Step 3. Create the routing list_ @@ -196 +196 @@ Potential issues, including other listener issues or network access issues.| See -**Step 4. Validate the routing list** + _Step 4. Validate the routing list_ @@ -201 +201 @@ Potential issues, including other listener issues or network access issues.| See -**Step 5. SQL Command Utility** + _Step 5. SQL Command Utility_