Skip to content

Commit 0525b34

Browse files
committed
Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into nw-nsgflow
2 parents 1dad19e + daf4a2c commit 0525b34

File tree

1 file changed

+11
-12
lines changed

1 file changed

+11
-12
lines changed

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

Lines changed: 11 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ description: Learn about limitations and known issues with Azure Synapse Link fo
44
author: jonburchel
55
ms.author: jburchel
66
ms.reviewer: jburchel, chuckheinzelman, wiassaf, imotiwala
7-
ms.date: 05/02/2024
7+
ms.date: 07/24/2024
88
ms.service: synapse-analytics
99
ms.subservice: synapse-link
1010
ms.topic: troubleshooting
@@ -61,18 +61,17 @@ The following sections list limitations for Azure Synapse Link for SQL.
6161
- System tables can't be replicated.
6262
- The security configuration from the source database will **NOT** be reflected in the target dedicated SQL pool.
6363
- Enabling Azure Synapse Link for SQL creates a new schema named `changefeed`. Don't use this schema, as it is reserved for system use.
64-
- Source tables with collations that are unsupported by dedicated SQL pools, such as UTF-8 and certain Japanese collations, can't be replicated. Here's the [supported collations in Synapse SQL Pool](../sql/reference-collation-types.md).
65-
* Additionally, Azure Synapse Link for SQL does not support some Thai language collations:
66-
* **Thai100CaseInsensitiveAccentInsensitiveKanaSensitive**
67-
* **Thai100CaseInsensitiveAccentSensitiveSupplementaryCharacters**
68-
* **Thai100CaseSensitiveAccentInsensitiveKanaSensitive**
69-
* **Thai100CaseSensitiveAccentInsensitiveKanaSensitiveWidthSensitiveSupplementaryCharacters**
70-
* **Thai100CaseSensitiveAccentSensitiveKanaSensitive**
71-
* **Thai100CaseSensitiveAccentSensitiveSupplementaryCharacters**
72-
* **ThaiCaseSensitiveAccentInsensitiveWidthSensitive**
73-
* Currently, the collation **Latin1_General_BIN2** isn't supported as there's a known issue where the link can't be stopped nor underlying tables could be removed from replication.
64+
- Source tables with collations that are unsupported by dedicated SQL pools, such as UTF-8 and certain Japanese collations, can't be replicated. See [supported collations in Synapse SQL pools](../sql/reference-collation-types.md).
65+
* Additionally, Azure Synapse Link for SQL does not support some Thai language collations:
66+
* `Thai100CaseInsensitiveAccentInsensitiveKanaSensitive`
67+
* `Thai100CaseInsensitiveAccentSensitiveSupplementaryCharacters`
68+
* `Thai100CaseSensitiveAccentInsensitiveKanaSensitive`
69+
* `Thai100CaseSensitiveAccentInsensitiveKanaSensitiveWidthSensitiveSupplementaryCharacters`
70+
* `Thai100CaseSensitiveAccentSensitiveKanaSensitive`
71+
* `Thai100CaseSensitiveAccentSensitiveSupplementaryCharacters`
72+
* `ThaiCaseSensitiveAccentInsensitiveWidthSensitive`
7473
- Single row updates (including off-page storage) of > 370 MB are not supported.
75-
- When Azure Synapse Link for SQL on Azure SQL Database or SQL Server 2022 is enabled, the aggressive log truncation feature of Accelerated Database Recovery (ADR) is automatically disabled. This is because Azure Synapse Link for SQL accesses the database transaction log. This behavior is similar to changed data capture (CDC). Active transactions continue to hold the transaction log truncation until the transaction commits and Azure Synapse Link for SQL catches up, or transaction aborts. This might result in the transaction log filling up more than usual and should be monitored so that the transaction log does not fill.
74+
- When Azure Synapse Link for SQL on Azure SQL Database or SQL Server 2022 is enabled, the aggressive log truncation feature of Accelerated Database Recovery (ADR) is automatically disabled. This is necessary because Azure Synapse Link for SQL accesses the database transaction log. This behavior is similar to changed data capture (CDC). Active transactions continue to hold the transaction log truncation until the transaction commits and Azure Synapse Link for SQL catches up, or transaction aborts. This might result in the transaction log filling up more than usual and should be monitored so that the transaction log does not fill.
7675

7776
### Azure SQL Database only
7877
- Azure Synapse Link for SQL isn't supported on Free, Basic, or Standard tier with fewer than 100 DTUs.

0 commit comments

Comments
 (0)