Skip to content

Commit 18a53db

Browse files
committed
formatting
1 parent cca3bf0 commit 18a53db

File tree

1 file changed

+5
-6
lines changed

1 file changed

+5
-6
lines changed

articles/virtual-machines/windows/sql/virtual-machines-windows-sql-workgroup-availability-group.md

Lines changed: 5 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -19,7 +19,7 @@ ms.author: mathoma
1919
---
2020
# Configure a workgroup availability group
2121

22-
This article explains the steps necessary to create an Active Directory Domain-independent cluster with an Always On availability group; this is also known as a workgroup cluster. This article focuses on the steps that are relevant to preparing and configuring the workgroup and availability group, and glosses over steps that are covered in other articles, such as how to create the cluster, or deploy the availability group.
22+
This article explains the steps necessary to create an Active Directory domain-independent cluster with an Always On availability group; this is also known as a workgroup cluster. This article focuses on the steps that are relevant to preparing and configuring the workgroup and availability group, and glosses over steps that are covered in other articles, such as how to create the cluster, or deploy the availability group.
2323

2424

2525
## Prerequisites
@@ -30,15 +30,14 @@ To configure a workgroup availability group, you need the following:
3030
- An account on each machine in the administrator group that also has sysadmin rights within SQL Server.
3131
- Open ports: TCP 1433, TCP 5022, TCP 59999.
3232

33-
For reference, the following parameters are used in this article:
33+
For reference, the following parameters are used in this article, but can be modified as is necessary:
3434

3535
| **Name** | **Parameter** |
3636
| :------ | :---------------------------------- |
3737
| **Node1** | AGNode1 (10.0.0.4) |
3838
| **Node2** | AGNode2 (10.0.0.5) |
3939
| **Cluster name** | AGWGAG (10.0.0.6) |
4040
| **Listener** | AGListener (10.0.0.7) |
41-
| **User account** | SQLAGADMIN|
4241
| **DNS Suffix** | ag.wgcluster.example.com |
4342
| **Work group name** | AGWorkgroup |
4443
|   |   |
@@ -112,7 +111,7 @@ Notable differences between the tutorial and what should be done for a workgroup
112111

113112
Once the cluster has been created, assign a static Cluster IP address. To do so, follow these steps:
114113

115-
1. On one of the nodes, open **Failover Cluster Manager**, select the cluster, right-click on the **Name: \<ClusterNam>** under **Cluster Core Resources** and then select **Properties**.
114+
1. On one of the nodes, open **Failover Cluster Manager**, select the cluster, right-click the **Name: \<ClusterNam>** under **Cluster Core Resources** and then select **Properties**.
116115

117116
![Launch properties for the cluster name](media/virtual-machines-windows-sql-workgroup-availability-group/5-launch-cluster-name-properties.png)
118117

@@ -158,7 +157,7 @@ To configure the first node, follow these steps:
158157
GO
159158
```
160159

161-
1. Next, create the HADR endpoint, and use the certificate for authentication by running this Transact-SQL statement:
160+
1. Next, create the HADR endpoint, and use the certificate for authentication by running this Transact-SQL (T-SQL) statement:
162161

163162
```sql
164163
--CREATE or ALTER the mirroring endpoint
@@ -199,7 +198,7 @@ To configure the second node, follow these steps:
199198
GO
200199
```
201200

202-
1. Next, create the HADR endpoint, and use the certificate for authentication by running this Transact-SQL statement:
201+
1. Next, create the HADR endpoint, and use the certificate for authentication by running this Transact-SQL (T-SQL) statement:
203202

204203
```sql
205204
--CREATE or ALTER the mirroring endpoint

0 commit comments

Comments
 (0)