Merge pull request #217561 from dearandyxu/master

pause/resume

Author: prmerger-automator[bot]

articles/synapse-analytics/synapse-link/faq.yml

@@ -40,7 +40,7 @@ sections:
       - question: |
           Can I pause the data replication from my link connection, and then resume it from where it is paused?
         answer: |
-          No, you cannot. Pausing and resuming a link connection will be coming soon.
+          Yes, you can.
       - question: |
           Can I select managed virtual network in Synapse workspace with Synapse managed private endpoints which allow the link connection to privately connect to the source database?
         answer: |

articles/synapse-analytics/synapse-link/sql-database-synapse-link.md

@@ -24,7 +24,7 @@ This article helps you to understand the functions of Azure Synapse Link for Azu
 
 A link connection identifies a mapping relationship between an Azure SQL database and an Azure Synapse Analytics dedicated SQL pool. You can create, manage, monitor and delete link connections in your Synapse workspace. When creating a link connection, you can select both source database and a destination Synapse dedicated SQL pool so that the operational data from your source database will be automatically replicated to the specified destination Synapse dedicated SQL pool. You can also add or remove one or more tables from your source database to be replicated.
 
-You can start or stop a link connection. When started, a link connection will start from a full initial load from your source database followed by incremental change feeds via the change feed feature in Azure SQL database. When you stop a link connection, the updates made to the operational data won't be synchronized to your Synapse dedicated SQL pool. For more information, see [Azure Synapse Link change feed for SQL Server 2022 and Azure SQL Database](/sql/sql-server/synapse-link/synapse-link-sql-server-change-feed).
+You can start, stop, pause or resume a link connection. When started, a link connection will start from a full initial load from your source database followed by incremental change feeds via the change feed feature in Azure SQL database. When you stop a link connection, the updates made to the operational data won't be synchronized to your Synapse dedicated SQL pool. It will do a full initial load from your source database if you start the link connection again. When you pause a link connection, the updates made to the operational data won't be synchronized to your Synapse dedicated SQL pool. When you resume a link connection, it will continue to synchronize the update from the place where you paused the link connection to your Synapse dedicated SQL pool. For more information, see [Azure Synapse Link change feed for SQL Server 2022 and Azure SQL Database](/sql/sql-server/synapse-link/synapse-link-sql-server-change-feed).
 
 You need to select compute core counts for each link connection to replicate your data. The core counts represent the compute power and it impacts your data replication latency and cost.
 
@@ -37,8 +37,11 @@ You can monitor Azure Synapse Link for SQL at the link and table levels. For eac
 * **Initial:** a link connection is created but not started. You will not be charged in initial state.
 * **Starting:** a link connection is setting up compute engines to replicate data.
 * **Running:** a link connection is replicating data.
-* **Stopping:** a link connection is shutting down the compute engines.
+* **Stopping:** a link connection is going to be stopped. The compute engine is being shut down. 
 * **Stopped:** a link connection is stopped. You will not be charged in stopped state.
+* **Pausing:** a link connection is going to be paused. The compute engine is being shut down. 
+* **Paused:** a link connection is paused. You will not be charged in paused state.
+* **Resuming:** a link connection is going to be resumed by setting up compute engines to continue to replicate the changes.
 
 For each table, you'll see the following status:
 

articles/synapse-analytics/synapse-link/sql-server-2022-synapse-link.md

@@ -24,7 +24,7 @@ This article helps you to understand the functions of Azure Synapse Link for SQL
 
 A link connection identifies a mapping relationship between an SQL Server 2022 and an Azure Synapse Analytics dedicated SQL pool. You can create, manage, monitor and delete link connections in your Synapse workspace. When creating a link connection, you can select both source database and destination Synapse dedicated SQL pool so that the operational data from your source database will be automatically replicated to the specified destination Synapse dedicated SQL pool. You can also add or remove one or more tables from your source database to be replicated.
 
-You can start or stop a link connection. When started, a link connection will start from a full initial load from your source database followed by incremental change feeds via change feed feature in SQL Server 2022. When you stop a link connection, the updates made to the operational data won't be synchronized to your Synapse dedicated SQL pool. For more information, see [Azure Synapse Link change feed for SQL Server 2022 and Azure SQL Database](/sql/sql-server/synapse-link/synapse-link-sql-server-change-feed).
+You can start, stop, pause or resume a link connection. When started, a link connection will start from a full initial load from your source database followed by incremental change feeds via change feed feature in SQL Server 2022. When you stop a link connection, the updates made to the operational data won't be synchronized to your Synapse dedicated SQL pool. It will do a full initial load from your source database if you start the link connection again. When you pause a link connection, the updates made to the operational data won't be synchronized to your Synapse dedicated SQL pool. When you resume a link connection, it will continue to synchronize the update from the place where you paused the link connection to your Synapse dedicated SQL pool. For more information, see [Azure Synapse Link change feed for SQL Server 2022 and Azure SQL Database](/sql/sql-server/synapse-link/synapse-link-sql-server-change-feed).
 
 You need to select compute core counts for each link connection to replicate your data. The core counts represent the compute power and it impacts your data replication latency and cost.
 
@@ -47,8 +47,11 @@ You can monitor Azure Synapse Link for SQL at the link and table levels. For eac
 * **Initial:** a link connection is created but not started. You will not be charged in initial state.
 * **Starting:** a link connection is setting up compute engines to replicate data.
 * **Running:** a link connection is replicating data.
-* **Stopping:** a link connection is shutting down the compute engines.
+* **Stopping:** a link connection is going to be stopped. The compute engine is being shut down. 
 * **Stopped:** a link connection is stopped. You will not be charged in stopped state.
+* **Pausing:** a link connection is going to be paused. The compute engine is being shut down. 
+* **Paused:** a link connection is paused. You will not be charged in paused state.
+* **Resuming:** a link connection is going to be resumed by setting up compute engines to continue to replicate the changes.
 
 For each table, you'll see the following status: