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
This tutorial shows you how to create a SQL Server availability group that uses Azure Resource Manager virtual machines. The tutorial uses Azure blades to configure a template. You can review the default settings, type required settings, and update the blades in the portal as you walk through this tutorial.
25
+
This tutorial shows you how to create a SQL Server availability group that uses Azure Resource Manager virtual machines (VM). The tutorial uses Azure blades to configure a template. You can review the default settings, type required settings, and update the blades in the portal as you walk through this tutorial.
25
26
26
27
The complete tutorial creates a SQL Server availability group on Azure Virtual Machines that include the following elements:
27
28
@@ -46,7 +47,6 @@ Before you start this tutorial, confirm the following:
46
47
> [!NOTE]
47
48
> If you are interested in using availability groups with SharePoint, also see [Configure SQL Server 2012 Always On availability groups for SharePoint 2013](/SharePoint/administration/configure-an-alwayson-availability-group).
48
49
>
49
-
>
50
50
51
51
In this tutorial, use the Azure portal to:
52
52
@@ -58,18 +58,20 @@ In this tutorial, use the Azure portal to:
5. On **Select a deployment model**, choose **Resource Manager**.
70
71
71
72
### Basics
72
-
Click **Basics** and configure the following settings:
73
+
74
+
Select **Basics** and configure the following settings:
73
75
74
76
***Administrator user name** is a user account that has domain administrator permissions and is a member of the SQL Server sysadmin fixed server role on both instances of SQL Server. For this tutorial, use **DomainAdmin**.
75
77
***Password** is the password for the domain administrator account. Use a complex password. Confirm the password.
@@ -81,10 +83,11 @@ The following screenshot is a completed **Basics** blade:
This Azure gallery template creates a domain and domain controllers. It also creates a network and two subnets. The template cannot create servers in an existing domain or virtual network. The next step configures the domain and network settings.
89
+
90
+
This Azure gallery template creates a domain and domain controllers. It also creates a network and two subnets. The template can't create servers in an existing domain or virtual network. The next step configures the domain and network settings.
88
91
89
92
On the **Domain and network settings** blade, review the preset values for the domain and network settings:
90
93
@@ -101,9 +104,10 @@ The **Domain and network settings** should look like the following screenshot:
101
104
102
105
If necessary, you can change these values. For this tutorial, use the preset values.
103
106
104
-
Review the settings, and then click**OK**.
107
+
Review the settings, and then select**OK**.
105
108
106
109
### Availability group settings
110
+
107
111
On **Availability group settings**, review the preset values for the availability group and the listener.
108
112
109
113
***Availability group name** is the clustered resource name for the availability group. For this tutorial, use **Contoso-ag**.
@@ -114,19 +118,21 @@ If necessary, you can change these values. For this tutorial, use the preset val
114
118
115
119

116
120
117
-
Click**OK**.
121
+
Select**OK**.
118
122
119
123
### Virtual machine size, storage settings
120
-
On **VM size, storage settings**, choose a SQL Server virtual machine size, and review the other settings.
121
124
122
-
***SQL Server virtual machine size** is the size for both virtual machines that run SQL Server. Choose an appropriate virtual machine size for your workload. If you are building this environment for the tutorial, use **DS2**. For production workloads, choose a virtual machine size that can support the workload. Many production workloads require **DS4** or larger. The template builds two virtual machines of this size and installs SQL Server on each one. For more information, see [Sizes for virtual machines](../../../virtual-machines/windows/sizes.md).
125
+
On**VM size, storage settings**, choose a SQL Server virtual machine size, and review the other settings.
***SQL Server virtual machine size** is the size for both virtual machines that run SQL Server. Choose an appropriate virtual machine size for your workload.
128
+
* If you are building this environment for the tutorial, use **DS2**.
129
+
* For production workloads, choose a virtual machine size that can support the workload.
130
+
* Many production workloads require **DS4** or larger. The template builds two virtual machines of this size and installs SQL Server on each one.
131
+
* For more information, see [Sizes for virtual machines](../../../virtual-machines/windows/sizes.md).
125
132
126
-
> [!NOTE]
127
-
> Azure installs the Enterprise Edition of SQL Server. The cost depends on the edition and the virtual machine size. For detailed information about current costs, see [virtual machines pricing](https://azure.microsoft.com/pricing/details/virtual-machines/#Sql).
128
-
>
129
-
>
133
+
> [!NOTE]
134
+
> Azure installs the Enterprise Edition of SQL Server. The cost depends on the edition and the virtual machine size. For detailed information about current costs, see [virtual machines pricing](https://azure.microsoft.com/pricing/details/virtual-machines/#Sql).
135
+
>
130
136
131
137
***Domain controller virtual machine size** is the virtual machine size for the domain controllers. For this tutorial use **D2**.
132
138
***File Share Witness virtual machine size** is the virtual machine size for the file share witness. For this tutorial, use **A1**.
@@ -143,18 +149,18 @@ For this tutorial, use **General workload**.
Additional optimizations depend on the size of the SQL Server data disks. For each terabyte of data disk, Azure adds an additional 1 TB premium storage. When a server requires 2 TB or more, the template creates a storage pool on each SQL Server virtual machine. A storage pool is a form of storage virtualization where multiple discs are configured to provide higher capacity, resiliency, and performance. The template then creates a storage space on the storage pool and presents a single data disk to the operating system. The template designates this disk as the data disk for SQL Server. The template tunes the storage pool for SQL Server by using the following settings:
150
157
151
158
* Stripe size is the interleave setting for the virtual disk. Transactional workloads use 64 KB. Data warehousing workloads use 256 KB.
152
159
* Resiliency is simple (no resiliency).
153
160
154
-
> [!NOTE]
155
-
> Azure premium storage is locally redundant and keeps three copies of the data within a single region, so additional resiliency at the storage pool is not required.
156
-
>
157
-
>
161
+
> [!NOTE]
162
+
> Azure premium storage is locally redundant and keeps three copies of the data within a single region, so additional resiliency at the storage pool is not required.
163
+
>
158
164
159
165
* Column count equals the number of disks in the storage pool.
160
166
@@ -167,48 +173,52 @@ For more information about SQL Server configuration best practices, see
167
173
[Performance best practices for SQL Server in Azure virtual machines](performance-guidelines-best-practices.md).
168
174
169
175
### SQL Server settings
176
+
170
177
On **SQL Server settings**, review and modify the SQL Server virtual machine name prefix, SQL Server version, SQL Server service account and password, and the SQL auto-patching maintenance schedule.
171
178
172
179
***SQL Server Name Prefix** is used to create a name for each SQL Server virtual machine. For this tutorial, use **sqlserver**. The template names the SQL Server virtual machines *sqlserver-0* and *sqlserver-1*.
173
180
***SQL Server version** is the version of SQL Server. For this tutorial use **SQL Server 2014**. You can also choose **SQL Server 2012** or **SQL Server 2016**.
174
181
***SQL Server service account user name** is the domain account name for the SQL Server service. For this tutorial, use **sqlservice**.
175
-
***Password** is the password for the SQL Server service account. Use a complex password. Confirm the password.
182
+
***Password** is the password for the SQL Server service account. Use a complex password. Confirm the password.
176
183
***SQL Auto Patching maintenance schedule** identifies the day of the week that Azure automatically patches the SQL Servers. For this tutorial, type **Sunday**.
177
184
***SQL Auto Patching maintenance start hour** is the time of day for the Azure region when automatic patching begins.
178
185
179
186
> [!NOTE]
180
187
> The patching window for each virtual machine is staggered by one hour. Only one virtual machine is patched at a time to prevent disruption of services.
181
188
>
182
-
>
183
189
184
190

185
191
186
-
Review the settings, and then click**OK**.
192
+
Review the settings, and then select**OK**.
187
193
188
194
### Summary
189
-
On the summary page, Azure validates the settings. You can also download the template. Review the summary. Click **OK**.
195
+
196
+
On the summary page, Azure validates the settings. You can also download the template. Review the summary. Select **OK**.
190
197
191
198
### Buy
192
-
This final blade contains **terms of use**, and **privacy policy**. Review this information. When you are ready for Azure to start to create the virtual machines and all the other required resources for the availability group, click **Create**.
199
+
200
+
This final blade contains **terms of use**, and **privacy policy**. Review this information. When you are ready for Azure to start to create the virtual machines and all the other required resources for the availability group, select **Create**.
193
201
194
202
The Azure portal creates the resource group and all the resources.
195
203
196
204
## Monitor deployment
205
+
197
206
Monitor the deployment progress from the Azure portal. An icon that represents the deployment is automatically pinned to the Azure portal dashboard.
The new instances of SQL Server are running on virtual machines that have internet-connected IP addresses. You can remote desktop (RDP) directly to each SQL Server virtual machine.
203
211
204
-
To RDP to a SQL Server, follow these steps:
212
+
The new instances of SQL Server are running on virtual machines that have internet-connected IP addresses. You can connect directly to each SQL Server virtual machine with remote desktop (RDP).
213
+
214
+
To use RDP to connect to a SQL Server VM, follow these steps:
205
215
206
216
1. From the Azure portal dashboard, verify that the deployment has succeeded.
207
-
2.Click**Resources**.
208
-
3. In the **Resources** blade, click**sqlserver-0**, which is the computer name of one of the virtual machines that's running SQL Server.
209
-
4. On the blade for **sqlserver-0**, click**Connect**. Your browser asks if you want to open or save the remote connection object. Click**Open**.
210
-
5.**Remote desktop connection** might warn you that the publisher of this remote connection can’t be identified. Click**Connect**.
211
-
6. Windows security prompts you to enter your credentials to connect to the IP address of the primary domain controller. Click**Use another account**. For **User name**, type **contoso\DomainAdmin**. You configured this account when you set the administrator user name in the template. Use the complex password that you chose when you configured the template.
212
-
7.**Remote desktop** might warn you that the remote computer could not be authenticated due to problems with its security certificate. It shows you the security certificate name. If you followed the tutorial, the name is **sqlserver-0.contoso.com**. Click**Yes**.
217
+
2.Select**Resources**.
218
+
3. In the **Resources** blade, select**sqlserver-0**, which is the computer name of one of the virtual machines that's running SQL Server.
219
+
4. On the blade for **sqlserver-0**, select**Connect**. Your browser asks if you want to open or save the remote connection object. Select**Open**.
220
+
5.**Remote desktop connection** might warn you that the publisher of this remote connection can’t be identified. Select**Connect**.
221
+
6. Windows security prompts you to enter your credentials to connect to the IP address of the primary domain controller. Select**Use another account**. For **User name**, type **contoso\DomainAdmin**. You configured this account when you set the administrator user name in the template. Use the complex password that you chose when you configured the template.
222
+
7.**Remote desktop** might warn you that the remote computer could not be authenticated due to problems with its security certificate. It shows you the security certificate name. If you followed the tutorial, the name is **sqlserver-0.contoso.com**. Select**Yes**.
213
223
214
224
You are now connected with RDP to the SQL Server virtual machine. You can open SQL Server Management Studio, connect to the default instance of SQL Server, and verify that the availability group is configured.
0 commit comments