Merge pull request #299798 from MicrosoftDocs/release-build-synapse-link-sql-server

Release build synapse link sql server

Author: thomps23

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

@@ -8,7 +8,7 @@ metadata:
   ms.service: azure-synapse-analytics
   ms.topic: faq
   ms.subservice: synapse-link
-  ms.date: 10/21/2024
+  ms.date: 05/07/2025
   ms.custom: references_regions
 title: Azure Synapse Link for SQL FAQ
 summary: In this guide, find the most frequently asked questions for Azure Synapse Link for SQL.
@@ -23,7 +23,7 @@ sections:
       - question: |
           Does Azure Synapse Link for SQL support Azure SQL Managed Instance as a source store?
         answer: |
-          No, currently Azure Synapse Link for SQL only supports Azure SQL Database and SQL Server (starting with SQL Server 2022) as the source.
+          No, currently Azure Synapse Link for SQL only supports Azure SQL Database and SQL Server 2022 as the source.
       - question: |
           Do I need to stop the link connection when I want to add or remove tables to be replicated?
         answer: |
@@ -124,18 +124,18 @@ sections:
         answer: |
           A new change feed processor has been integrated into the Azure SQL Database and SQL Server 2022 engine to enable this functionality.
       - question: |
-          How do I rotate or change the SAS for the Landing Zone for Azure Synapse Link for SQL Server?
+          How do I rotate or change the SAS for the Landing Zone for Azure Synapse Link for SQL Server 2022?
         answer: |
           If the SAS has expired for the user managed storage account for the Landing Zone, use [ALTER DATABASE SCOPED CREDENTIAL](/sql/t-sql/statements/alter-database-scoped-credential-transact-sql) to update the database credential for the new SAS. 
       - question: |
           What is the impact when a user removes the Azure Synapse workspace that contains an Azure Synapse Link to Azure SQL Database?
         answer: |
           If the Azure Synapse workspace is removed, Azure SQL Database will stop data replication from landing zone into Azure Synapse. The system stored procedure [sp_change_feed_drop_table_group](/sql/relational-databases/system-stored-procedures/sp-change-feed-drop-table-group) will be called automatically, and the storage account for the landing zone is managed and will be cleaned up automatically. If this fails, you might receive error 22739 from the SynapseGatewayClient in [sys.dm_change_feed_errors](/sql/relational-databases/system-dynamic-management-views/sys-dm-change-feed-errors). If this occurs, you can manually drop the `changefeed` table group with `sp_change_feed_drop_table_group`.
       - question: |
-          What is the impact when a user removes the Azure Synapse workspace that contains an Azure Synapse Link for SQL Server?
+          What is the impact when a user removes the Azure Synapse workspace that contains an Azure Synapse Link for SQL Server 2022?
         answer: | 
-          In SQL Server, since landing zone storage account is user managed, data will continue to be published to the landing zone. You should disable the Azure Synapse Link by dropping the relevant table groups with [sp_change_feed_drop_table_group](/sql/relational-databases/system-stored-procedures/sp-change-feed-drop-table-group), and manually remove the storage account for the landing zone.
+          In SQL Server 2022, since landing zone storage account is user managed, data will continue to be published to the landing zone. You should disable the Azure Synapse Link by dropping the relevant table groups with [sp_change_feed_drop_table_group](/sql/relational-databases/system-stored-procedures/sp-change-feed-drop-table-group), and manually remove the storage account for the landing zone.
       - question: |
-          What is the impact when a user intentionally removes the Azure Synapse Link landing zone for Azure Synapse Link for SQL Server?
+          What is the impact when a user intentionally removes the Azure Synapse Link landing zone for Azure Synapse Link for SQL Server 2022?
         answer: | 
-          In SQL Server, the landing zone storage account is user managed. If the landing zone storage account is no longer accessible, you will see errors in the [sys.dm_change_feed_errors](/sql/relational-databases/system-dynamic-management-views/sys-dm-change-feed-errors). You should disable the Azure Synapse Link by dropping the relevant table groups with [sp_change_feed_drop_table_group](/sql/relational-databases/system-stored-procedures/sp-change-feed-drop-table-group).
+          In SQL Server 2022, the landing zone storage account is user managed. If the landing zone storage account is no longer accessible, you will see errors in the [sys.dm_change_feed_errors](/sql/relational-databases/system-dynamic-management-views/sys-dm-change-feed-errors). You should disable the Azure Synapse Link by dropping the relevant table groups with [sp_change_feed_drop_table_group](/sql/relational-databases/system-stored-procedures/sp-change-feed-drop-table-group).

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

@@ -1,11 +1,11 @@
 ---
 title: Azure Synapse Link for Azure SQL Database
-description: Learn about Azure Synapse Link for Azure SQL Database, the link connection, and monitoring the Synapse Link.
+description: Learn about Azure Synapse Link for Azure SQL Database, the link connection, and monitoring the Azure Synapse Link.
 author: Rodrigossz
 ms.service: azure-synapse-analytics
 ms.topic: conceptual
 ms.subservice: synapse-link
-ms.date: 11/16/2022
+ms.date: 05/07/2025
 ms.author: rosouz
 ---
 
@@ -15,13 +15,16 @@ This article helps you to understand the functions of Azure Synapse Link for Azu
 
 ## Link connection
 
-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.
+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, 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 can start, stop, pause, or resume a link connection. When started, a link connection starts 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.
 
-You also have the chance to make a trade-off between cost and latency by selecting the continuous or batch mode to replicate the data.  When you select continuous mode, the runtime will be running continuously so that any changes applied to your SQL DB or SQL Server will be replicated to Synapse with low latency. When you select batch mode with specified interval, the changes applied to your SQL DB or SQL Server will be accumulated and replicated to Synapse in a batch mode with specified interval.  By doing so, you can save cost as you are only charged for the time when the runtime is required to replicate your data. After each batch of data is replicated, the runtime will be shut down automatically.
+You also have the chance to make a trade-off between cost and latency by selecting the continuous or batch mode to replicate the data. 
+
+- When you select continuous mode, the runtime runs continuously so that any changes applied to your Azure SQL Database or SQL Server 2022 instance will be replicated to Synapse with low latency. 
+- When you select batch mode with specified interval, the changes applied to your Azure SQL Database or SQL Server 2022 instance will be accumulated and replicated to Synapse in a batch mode with specified interval. By doing so, you can save cost as you are only charged for the time when the runtime is required to replicate your data. After each batch of data is replicated, the runtime will be shut down automatically.
 
 ## Monitoring
 
@@ -45,11 +48,11 @@ For each table, you'll see the following status:
 
 You can also get the following metrics to enable advanced monitoring of the service:
 
-* **Link connection events:** number of link connection events including start, stop or failure.
-* **Link table event:** number of link table events including snapshot, removal or failure.
+* **Link connection events:** number of link connection events including start, stop, or failure.
+* **Link table event:** number of link table events including snapshot, removal, or failure.
 * **Link latency in second:** data processing latency in second.
-* **Link data processed data volume (bytes):** data volume in bytes processed by Synapse link for SQL.
-* **Link processed row:** row counts (changed) processed by Synapse Link for SQL.
+* **Link data processed data volume (bytes):** data volume in bytes processed by Azure Synapse Link for SQL.
+* **Link processed row:** row counts (changed) processed by Azure Synapse Link for SQL.
 
 For more information, see [Manage Synapse Link for SQL change feed](/sql/sql-server/synapse-link/synapse-link-sql-server-change-feed-manage).
 
@@ -63,4 +66,4 @@ A consolidated list of known limitations and issues can be found at [Known limit
 
 ## Next steps
 
-* To learn more, see how to [Configure Synapse Link for Azure SQL Database](connect-synapse-link-sql-database.md).
+* To learn more, see how to [Configure Azure Synapse Link for Azure SQL Database](connect-synapse-link-sql-database.md).

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

@@ -5,15 +5,15 @@ author: Rodrigossz
 ms.service: azure-synapse-analytics
 ms.topic: overview
 ms.subservice: synapse-link
-ms.date: 11/18/2024
+ms.date: 05/07/2025
 ms.author: rosouz
 ---
 
 # What is Azure Synapse Link for SQL?
 
 Azure Synapse Link for SQL enables near real time analytics over operational data in Azure SQL Database or SQL Server 2022. With a seamless integration between operational stores including Azure SQL Database and SQL Server 2022 and Azure Synapse Analytics, Azure Synapse Link for SQL enables you to run analytics, business intelligence and machine learning scenarios on your operational data with minimum impact on source databases with a new change feed technology.
 
-The following image shows the Azure Synapse Link integration with Azure SQL DB, SQL Server 2022, and Azure Synapse Analytics:
+The following image shows the Azure Synapse Link integration with Azure SQL Database, SQL Server 2022, and Azure Synapse Analytics:
 
 :::image type="content" source="../media/sql-synapse-link-overview/synapse-link-sql-architecture.png" alt-text="Diagram of the Azure Synapse Link for SQL architecture.":::
 

articles/synapse-analytics/synapse-link/synapse-link-for-sql-known-issues.md

@@ -4,7 +4,7 @@ description: Learn about limitations and known issues with Azure Synapse Link fo
 author: jonburchel
 ms.author: jburchel
 ms.reviewer: jburchel, chuckheinzelman, imotiwala
-ms.date: 07/24/2024
+ms.date: 05/07/2025
 ms.service: azure-synapse-analytics
 ms.subservice: synapse-link
 ms.topic: troubleshooting
@@ -28,7 +28,7 @@ The following sections list limitations for Azure Synapse Link for SQL.
   * **sql_variant**
   * **timestamp**
 - Source table row size can't exceed 7,500 bytes. For tables where variable-length columns are stored off-row, a 24-byte pointer is stored in the main record.
-- When source tables are being initially snapshotted, any source table data containing large object (LOB) data greater than 1 MB in size is not supported. These LOB data types include: **varchar(max)**, **nvarchar(max)**, **varbinary(max)**. An error is thrown and data is not exported to Azure Synapse Analytics. Use the stored procedure [sp_configure](/sql/database-engine/configure-windows/configure-the-max-text-repl-size-server-configuration-option) to increase the configured maximum value for `max text repl size` option, which defaults to 64 K. A configured value of `-1` indicates no limit, other than the limit imposed by the data type.
+- When source tables are being initially snapshotted, any source table data containing large object (LOB) data greater than 1 MB in size isn't supported. These LOB data types include: **varchar(max)**, **nvarchar(max)**, **varbinary(max)**. An error is thrown and data isn't exported to Azure Synapse Analytics. Use the stored procedure [sp_configure](/sql/database-engine/configure-windows/configure-the-max-text-repl-size-server-configuration-option) to increase the configured maximum value for `max text repl size` option, which defaults to 64 K. A configured value of `-1` indicates no limit, other than the limit imposed by the data type.
 - Tables enabled for Azure Synapse Link for SQL can have a maximum of 1,020 columns (not 1,024).
 - While a database can have multiple links enabled, a given table can't belong to multiple links.
 - When a database owner doesn't have a mapped login, Azure Synapse Link for SQL runs into an error when enabling a link connection. User can set database owner to a valid user with the `ALTER AUTHORIZATION` command to fix this issue.
@@ -50,7 +50,7 @@ The following sections list limitations for Azure Synapse Link for SQL.
   * Rename Table
 - If data definition language (DDL) + data manipulation language (DML) is executed in an explicit transaction (between `BEGIN TRANSACTION` and `END TRANSACTION` statements), replication for corresponding tables fails within the link connection.
   > [!NOTE]
-  > If a table is critical for transactional consistency at the link connection level, please review the state of the Azure Synapse Link table in the Monitoring tab.
+  > If a table is critical for transactional consistency at the link connection level, review the state of the Azure Synapse Link table in the Monitoring tab.
 - Azure Synapse Link for SQL can't be enabled if any of the following features are in use for the source table.
   * Change Data Capture
   * Temporal history table
@@ -89,6 +89,7 @@ The following sections list limitations for Azure Synapse Link for SQL.
 - With asynchronous replicas in an availability group, transactions must be written to all replicas before publishing to Azure Synapse Link for SQL.
 - Azure Synapse Link for SQL isn't supported on databases with database mirroring enabled.
 - Restoring an Azure Synapse Link for SQL-enabled database from on-premises to Azure SQL Managed Instance isn't supported.
+- Azure Synapse Link for SQL is not supported on SQL Server 2025 instances.
 
 > [!CAUTION]
 > Azure Synapse Link for SQL is not supported on databases that are also using Azure SQL Managed Instance Link. Caution that in these scenarios, when the managed instance transitions to read-write mode, you might encounter transaction log full issues.