You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/virtual-machines/windows/sql/virtual-machines-windows-sql-workgroup-availability-group.md
+5-6Lines changed: 5 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -19,7 +19,7 @@ ms.author: mathoma
19
19
---
20
20
# Configure a workgroup availability group
21
21
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.
23
23
24
24
25
25
## Prerequisites
@@ -30,15 +30,14 @@ To configure a workgroup availability group, you need the following:
30
30
- An account on each machine in the administrator group that also has sysadmin rights within SQL Server.
31
31
- Open ports: TCP 1433, TCP 5022, TCP 59999.
32
32
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:
34
34
35
35
|**Name**|**Parameter**|
36
36
| :------ | :---------------------------------- |
37
37
|**Node1**| AGNode1 (10.0.0.4) |
38
38
|**Node2**| AGNode2 (10.0.0.5) |
39
39
|**Cluster name**| AGWGAG (10.0.0.6) |
40
40
|**Listener**| AGListener (10.0.0.7) |
41
-
|**User account**| SQLAGADMIN|
42
41
|**DNS Suffix**| ag.wgcluster.example.com |
43
42
|**Work group name**| AGWorkgroup |
44
43
| | |
@@ -112,7 +111,7 @@ Notable differences between the tutorial and what should be done for a workgroup
112
111
113
112
Once the cluster has been created, assign a static Cluster IP address. To do so, follow these steps:
114
113
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**.
116
115
117
116

118
117
@@ -158,7 +157,7 @@ To configure the first node, follow these steps:
158
157
GO
159
158
```
160
159
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:
162
161
163
162
```sql
164
163
--CREATE or ALTER the mirroring endpoint
@@ -199,7 +198,7 @@ To configure the second node, follow these steps:
199
198
GO
200
199
```
201
200
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:
0 commit comments