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/mysql/howto-configure-server-parameters-using-cli.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@ ms.author: andrela
6
6
ms.service: mysql
7
7
ms.devlang: azurecli
8
8
ms.topic: conceptual
9
-
ms.date: 12/05/2019
9
+
ms.date: 3/18/2020
10
10
---
11
11
# Customize server parameters by using Azure CLI
12
12
You can list, show, and update configuration parameters for an Azure Database for MySQL server by using Azure CLI, the Azure command-line utility. A subset of engine configurations is exposed at the server-level and can be modified.
Copy file name to clipboardExpand all lines: articles/mysql/howto-configure-ssl.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@ author: ajlam
5
5
ms.author: andrela
6
6
ms.service: mysql
7
7
ms.topic: conceptual
8
-
ms.date: 12/05/2019
8
+
ms.date: 3/18/2020
9
9
---
10
10
# Configure SSL connectivity in your application to securely connect to Azure Database for MySQL
11
11
Azure Database for MySQL supports connecting your Azure Database for MySQL server to client applications using Secure Sockets Layer (SSL). Enforcing SSL connections between your database server and your client applications helps protect against "man in the middle" attacks by encrypting the data stream between the server and your application.
Copy file name to clipboardExpand all lines: articles/mysql/howto-data-in-replication.md
+11-11Lines changed: 11 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@ author: ajlam
5
5
ms.author: andrela
6
6
ms.service: mysql
7
7
ms.topic: conceptual
8
-
ms.date: 12/02/2019
8
+
ms.date: 3/18/2020
9
9
---
10
10
11
11
# How to configure Azure Database for MySQL Data-in Replication
@@ -39,9 +39,9 @@ The following steps prepare and configure the MySQL server hosted on-premises, i
39
39
SHOW VARIABLES LIKE'log_bin';
40
40
```
41
41
42
-
If the variable [`log_bin`](https://dev.mysql.com/doc/refman/8.0/en/replication-options-binary-log.html#sysvar_log_bin) is returned with the value “ON", binary logging is enabled on your server.
42
+
If the variable [`log_bin`](https://dev.mysql.com/doc/refman/8.0/en/replication-options-binary-log.html#sysvar_log_bin) is returned with the value "ON", binary logging is enabled on your server.
43
43
44
-
If `log_bin` is returned with the value “OFF”, turn on binary logging by editing your my.cnf file so that `log_bin=ON` and restart your server for the change to take effect.
44
+
If `log_bin` is returned with the value "OFF", turn on binary logging by editing your my.cnf file so that `log_bin=ON` and restart your server for the change to take effect.
45
45
46
46
2. Master server settings
47
47
@@ -104,7 +104,7 @@ The following steps prepare and configure the MySQL server hosted on-premises, i
104
104
5. Get binary log file name and offset
105
105
106
106
Run the [`show master status`](https://dev.mysql.com/doc/refman/5.7/en/show-master-status.html) command to determine the current binary log file name and offset.
107
-
107
+
108
108
```sql
109
109
show master status;
110
110
```
@@ -148,7 +148,7 @@ The following steps prepare and configure the MySQL server hosted on-premises, i
148
148
- master_password: password for the master server
149
149
- master_log_file: binary log file name from running `show master status`
150
150
- master_log_pos: binary log position from running `show master status`
151
-
- master_ssl_ca: CA certificate’s context. If not using SSL, pass in empty string.
151
+
- master_ssl_ca: CA certificate's context. If not using SSL, pass in empty string.
152
152
- It is recommended to pass this parameter in as a variable. See the following examples for more information.
153
153
154
154
> [!NOTE]
@@ -162,18 +162,18 @@ The following steps prepare and configure the MySQL server hosted on-premises, i
162
162
163
163
```sql
164
164
SET @cert ='-----BEGIN CERTIFICATE-----
165
-
PLACE YOUR PUBLIC KEY CERTIFICATE’S CONTEXT HERE
165
+
PLACE YOUR PUBLIC KEY CERTIFICATE'S CONTEXT HERE
166
166
-----END CERTIFICATE-----'
167
167
```
168
168
169
-
Replication with SSL is set up between a master server hosted in the domain “companya.com” and a replica server hosted in Azure Database for MySQL. This stored procedure is run on the replica.
169
+
Replication with SSL is set up between a master server hosted in the domain "companya.com" and a replica server hosted in Azure Database for MySQL. This stored procedure is run on the replica.
Replication without SSL is set up between a master server hosted in the domain “companya.com” and a replica server hosted in Azure Database for MySQL. This stored procedure is run on the replica.
176
+
Replication without SSL is set up between a master server hosted in the domain "companya.com" and a replica server hosted in Azure Database for MySQL. This stored procedure is run on the replica.
@@ -190,12 +190,12 @@ The following steps prepare and configure the MySQL server hosted on-premises, i
190
190
1. Check replication status
191
191
192
192
Call the [`show slave status`](https://dev.mysql.com/doc/refman/5.7/en/show-slave-status.html) command on the replica server to view the replication status.
193
-
193
+
194
194
```sql
195
195
show slave status;
196
196
```
197
197
198
-
If the state of `Slave_IO_Running` and `Slave_SQL_Running` are "yes" and the value of `Seconds_Behind_Master` is “0”, replication is working well. `Seconds_Behind_Master` indicates how late the replica is. If the value is not "0", it means that the replica is processing updates.
198
+
If the state of `Slave_IO_Running` and `Slave_SQL_Running` are "yes" and the value of `Seconds_Behind_Master` is "0", replication is working well. `Seconds_Behind_Master` indicates how late the replica is. If the value is not "0", it means that the replica is processing updates.
0 commit comments