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/synapse-analytics/synapse-link/sql-database-synapse-link.md
+9-9Lines changed: 9 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
---
2
2
title: Azure Synapse Link for Azure SQL Database
3
-
description: Learn about Azure Synapse Link for Azure SQL Database, the link connection, and monitoring the Synapse Link.
3
+
description: Learn about Azure Synapse Link for Azure SQL Database, the link connection, and monitoring the Azure Synapse Link.
4
4
author: Rodrigossz
5
5
ms.service: azure-synapse-analytics
6
6
ms.topic: conceptual
@@ -15,15 +15,15 @@ This article helps you to understand the functions of Azure Synapse Link for Azu
15
15
16
16
## Link connection
17
17
18
-
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.
18
+
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.
19
19
20
-
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).
20
+
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).
21
21
22
22
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.
23
23
24
24
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.
25
25
26
-
- When you select continuous mode, the runtime will be running continuously so that any changes applied to your Azure SQL Database or SQL Server 2022 instance will be replicated to Synapse with low latency.
26
+
- 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.
27
27
- 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.
28
28
29
29
## Monitoring
@@ -48,11 +48,11 @@ For each table, you'll see the following status:
48
48
49
49
You can also get the following metrics to enable advanced monitoring of the service:
50
50
51
-
***Link connection events:** number of link connection events including start, stop or failure.
52
-
***Link table event:** number of link table events including snapshot, removal or failure.
51
+
***Link connection events:** number of link connection events including start, stop, or failure.
52
+
***Link table event:** number of link table events including snapshot, removal, or failure.
53
53
***Link latency in second:** data processing latency in second.
54
-
***Link data processed data volume (bytes):** data volume in bytes processed by Synapse link for SQL.
55
-
***Link processed row:** row counts (changed) processed by Synapse Link for SQL.
54
+
***Link data processed data volume (bytes):** data volume in bytes processed by Azure Synapse Link for SQL.
55
+
***Link processed row:** row counts (changed) processed by Azure Synapse Link for SQL.
56
56
57
57
For more information, see [Manage Synapse Link for SQL change feed](/sql/sql-server/synapse-link/synapse-link-sql-server-change-feed-manage).
58
58
@@ -66,4 +66,4 @@ A consolidated list of known limitations and issues can be found at [Known limit
66
66
67
67
## Next steps
68
68
69
-
* To learn more, see how to [Configure Synapse Link for Azure SQL Database](connect-synapse-link-sql-database.md).
69
+
* To learn more, see how to [Configure Azure Synapse Link for Azure SQL Database](connect-synapse-link-sql-database.md).
Copy file name to clipboardExpand all lines: articles/synapse-analytics/synapse-link/synapse-link-for-sql-known-issues.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -28,7 +28,7 @@ The following sections list limitations for Azure Synapse Link for SQL.
28
28
***sql_variant**
29
29
***timestamp**
30
30
- 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.
31
-
- 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.
31
+
- 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.
32
32
- Tables enabled for Azure Synapse Link for SQL can have a maximum of 1,020 columns (not 1,024).
33
33
- While a database can have multiple links enabled, a given table can't belong to multiple links.
34
34
- 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.
50
50
* Rename Table
51
51
- 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.
52
52
> [!NOTE]
53
-
> 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.
53
+
> 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.
54
54
- Azure Synapse Link for SQL can't be enabled if any of the following features are in use for the source table.
0 commit comments