Merge pull request #188714 from SudheeshGH/GTIDSingle

Adding GTID Not supported to Single Server for Storage V1

Author: PRMerger19

articles/mysql/concepts-data-in-replication.md

@@ -39,6 +39,9 @@ To learn more about this parameter, review the [MySQL documentation](https://dev
 
 Data-in Replication is only supported in General Purpose and Memory Optimized pricing tiers.
 
+>[!Note]
+>GTID is supported on versions 5.7 and 8.0 and only on servers that support storage up to 16 TB (General purpose storage v2).
+
 ### Requirements
 
 - The source server version must be at least MySQL version 5.6.

articles/mysql/concepts-read-replicas.md

@@ -157,7 +157,7 @@ After your application is successfully processing reads and writes, you've compl
 
 ## Global transaction identifier (GTID)
 
-Global transaction identifier (GTID) is a unique identifier created with each committed transaction on a source server and is OFF by default in Azure Database for MySQL. GTID is supported on versions 5.7 and 8.0 and only on servers that support storage up to 16 TB. To learn more about GTID and how it's used in replication, refer to MySQL's [replication with GTID](https://dev.mysql.com/doc/refman/5.7/en/replication-gtids.html) documentation.
+Global transaction identifier (GTID) is a unique identifier created with each committed transaction on a source server and is OFF by default in Azure Database for MySQL. GTID is supported on versions 5.7 and 8.0 and only on servers that support storage up to 16 TB(General purpose storage v2). To learn more about GTID and how it's used in replication, refer to MySQL's [replication with GTID](https://dev.mysql.com/doc/refman/5.7/en/replication-gtids.html) documentation.
 
 MySQL supports two types of transactions: GTID transactions (identified with GTID) and anonymous transactions (don't have a GTID allocated)
 

articles/mysql/howto-data-in-replication.md

@@ -28,6 +28,7 @@ Review the [limitations and requirements](concepts-data-in-replication.md#limita
 
    > [!IMPORTANT]
    > The Azure Database for MySQL server must be created in the General Purpose or Memory Optimized pricing tiers as data-in replication is only supported in these tiers.
+   > GTID is supported on versions 5.7 and 8.0 and only on servers that support storage up to 16 TB (General purpose storage v2).
 
 2. Create the same user accounts and corresponding privileges.
 
@@ -341,6 +342,9 @@ call mysql. az_replication_skip_gtid_transaction(‘<transaction_gtid>’)
 
 The procedure can skip the transaction for the given GTID. If the GTID format is not right or the GTID transaction has already been executed, the procedure will fail to execute. The GTID for a transaction can be determined by parsing the binary log to check the transaction events. MySQL provides a utility [mysqlbinlog](https://dev.mysql.com/doc/refman/5.7/en/mysqlbinlog.html) to parse binary logs and display their contents in text format, which can be used to identify GTID of the transaction.
 
+>[!Important]
+>This procedure can be only used to skip one transaction, and can't be used to skip gtid set or set gtid_purged.
+
 To skip the next transaction after the current replication position, use the following command to identify the GTID of next transaction as shown below.
 
 ```sql