Skip to content

Commit 40846ae

Browse files
WilliamDAssafMSFTWilliamDAssafMSFT
committed
20241202 add link, edit pass
1 parent 548dcb4 commit 40846ae

File tree

1 file changed

+23
-24
lines changed

1 file changed

+23
-24
lines changed

‎articles/synapse-analytics/synapse-link/troubleshoot/troubleshoot-sql-snapshot-issues.md

Lines changed: 23 additions & 24 deletions
Original file line numberDiff line numberDiff line change
@@ -1,33 +1,32 @@
11
---
2-
title: Troubleshooting guide for Azure Synapse Link initial snapshot issues for Azure SQL Database and SQL Server
2+
title: Troubleshooting Guide for Azure Synapse Link Initial Snapshot Issues for Azure SQL Database and SQL Server
33
description: Learn how to troubleshoot Azure Synapse Link initial snapshot issues for Azure SQL Database and SQL Server
44
author: WilliamDAssafMSFT
55
ms.author: wiassaf
66
ms.reviewer: imotiwala, prpasunu
7+
ms.date: 12/02/2024
78
ms.service: azure-synapse-analytics
8-
ms.topic: how-to
99
ms.subservice: synapse-link
10-
ms.date: 05/03/2023
10+
ms.topic: how-to
1111
---
1212

13-
# Troubleshoot: Azure Synapse Link for SQL initial snapshot issues
13+
# Troubleshoot: Azure Synapse Link for SQL initial snapshot issues
1414

1515
This article is a guide to troubleshooting issues with initial snapshot on Azure Synapse Link for Azure SQL Database and SQL Server.
1616

17-
## Pre-requisite
18-
Please ensure your configuration is accurate. https://learn.microsoft.com/en-us/azure/synapse-analytics/synapse-link/connect-synapse-link-sql-database#configure-your-source-azure-sql-database
17+
Start by reviewing your configuration. For more information, see [Configure your source Azure SQL database](../connect-synapse-link-sql-database.md#configure-your-source-azure-sql-database).
1918

2019
## Symptom
2120

22-
The users can follow the below resolution steps to investigate the below cases:
21+
The users can follow these resolution steps to investigate:
2322

2423
- Determine if a link connection snapshot state is stuck.
2524
- Determine if snapshot related errors are observed after starting the link connection.
2625
- Understand the progress of the initial snapshot for individual tables.
2726

2827
## Resolution
2928

30-
### Step 1: Query to get the current snapshot state for the tables included in the link connection
29+
### Step 1: Query to get the current snapshot state for the tables included in the link connection
3130

3231
Connect to the source database enabled for Azure Synapse Link using [SQL Server Management Studio](https://aka.ms/ssms) or [Azure Data Studio](https://aka.ms/azuredatastudio).
3332

@@ -42,17 +41,17 @@ FROM changefeed.change_feed_tables;
4241

4342
Example output:
4443

45-
:::image type="content" source="media/troubleshoot-sql-snapshot-issues/change-feed-tables-results-management-studio.png" alt-text="A screenshot from SQL Server Management Studio of the sample result set of the tables and columns from the changefeed.change_feed_tables system table." lightbox="media/troubleshoot-sql-snapshot-issues/change-feed-tables-results-management-studio.png":::
44+
:::image type="content" source="media/troubleshoot-sql-snapshot-issues/change-feed-tables-results-management-studio.png" alt-text="Screenshot from SQL Server Management Studio of the sample result set of the tables and columns from the changefeed.change_feed_tables system table." lightbox="media/troubleshoot-sql-snapshot-issues/change-feed-tables-results-management-studio.png":::
4645

4746
- If the `snapshot_phase` column value for the desired table is 6 (`EMIT_SNAPSHOT_ENDENTRY`), it means snapshot has already completed on the table and needs no further investigation.
48-
- There is a possibility that one of the phases of the snapshot may take longer to complete. Phase 5 (`EXPORT_DATA_FILE`) can be a time-consuming step. When the table size is large, the `EXPORT_DATA_FILE` phase is expected to take longer to finish. For more information on the snapshot phases, refer to [changefeed.change_feed_tables](/sql/relational-databases/system-tables/changefeed-change-feed-tables-transact-sql).
47+
- Steps of the snapshot can take longer to complete than others. Phase 5 (`EXPORT_DATA_FILE`) can be a time-consuming step. When the table size is large, the `EXPORT_DATA_FILE` phase is expected to take longer to finish. For more information on the snapshot phases, see [changefeed.change_feed_tables](/sql/relational-databases/system-tables/changefeed-change-feed-tables-transact-sql).
4948

5049
When a snapshot has not completed for a given table, there are two possible cases to consider based on the output of [changefeed.change_feed_tables](/sql/relational-databases/system-tables/changefeed-change-feed-tables-transact-sql):
5150

5251
- When `Snapshot_phase` < 6 and `snapshot_retry_count` = 0, the snapshot operation is ongoing, without error. No action is needed in this case, wait for snapshot completion.
5352
- When `Snapshot_phase` < 6 and `snapshot_retry_count` > 0, the snapshot operation has been failing and is being retried. Proceed to [Step 2](#step-2-snapshot-retry). For example, as in the following image:
5453

55-
:::image type="content" source="media/troubleshoot-sql-snapshot-issues/change-feed-tables-results-retries.png" alt-text="A screenshot from SQL Server Management Studio of the sample result set of the tables and columns from the changefeed.change_feed_tables system table, indicating retries." lightbox="media/troubleshoot-sql-snapshot-issues/change-feed-tables-results-retries.png":::
54+
:::image type="content" source="media/troubleshoot-sql-snapshot-issues/change-feed-tables-results-retries.png" alt-text="Screenshot from SQL Server Management Studio of the sample result set of the tables and columns from the changefeed.change_feed_tables system table, indicating retries." lightbox="media/troubleshoot-sql-snapshot-issues/change-feed-tables-results-retries.png":::
5655

5756
### Step 2: Snapshot retry
5857

@@ -64,22 +63,22 @@ SELECT * FROM sys.dm_change_feed_errors;
6463

6564
For example:
6665

67-
:::image type="content" source="media/troubleshoot-sql-snapshot-issues/change-feed-errors-results-management-studio.png" alt-text="A screenshot of the results of the sys.dm_change_feed_errors dynamic management view including possible snapshot errors to investigate." lightbox="media/troubleshoot-sql-snapshot-issues/change-feed-errors-results-management-studio.png":::
66+
:::image type="content" source="media/troubleshoot-sql-snapshot-issues/change-feed-errors-results-management-studio.png" alt-text="Screenshot of the results of the sys.dm_change_feed_errors dynamic management view including possible snapshot errors to investigate." lightbox="media/troubleshoot-sql-snapshot-issues/change-feed-errors-results-management-studio.png":::
6867

6968
1. If any errors are observed from the snapshot component when `source_task` = 5, refer to error specific mitigation details in the [Known limitations and issues with Azure Synapse Link for SQL](../synapse-link-for-sql-known-issues.md).
7069
1. If the error is not found in the known limitations article, [submit an Azure support request](https://portal.azure.com/#blade/Microsoft_Azure_Support/HelpAndSupportBlade/newsupportrequest) following the below instructions:
71-
1. For **Issue type**, select **Technical**.
72-
2. Provide the desired subscription of the source database. Select **Next**.
73-
3. For **Service type**, select **SQL Database**.
74-
4. For **Resource**, select the source database where the initial snapshot is failing.
75-
5. For **Summary**, provide the error numbers from `changefeed.change_feed_errors`.
76-
6. For **Problem type**, select **Data Sync, Replication, CDC and Change Tracking**.
77-
7. For **Problem subtype**, select **Transactional Replication**.
70+
1. For **Issue type**, select **Technical**.
71+
1. Provide the desired subscription of the source database. Select **Next**.
72+
1. For **Service type**, select **SQL Database**.
73+
1. For **Resource**, select the source database where the initial snapshot is failing.
74+
1. For **Summary**, provide the error numbers from `changefeed.change_feed_errors`.
75+
1. For **Problem type**, select **Data Sync, Replication, CDC and Change Tracking**.
76+
1. For **Problem subtype**, select **Transactional Replication**.
7877

79-
:::image type="content" source="media/troubleshoot-sql-snapshot-issues/sql-snapshot-issues-support-request.png" alt-text="A screenshot of the Azure portal where a New support request has been prepared.":::
78+
:::image type="content" source="media/troubleshoot-sql-snapshot-issues/sql-snapshot-issues-support-request.png" alt-text="Screenshot of the Azure portal where a New support request has been prepared.":::
8079

81-
## Next steps
80+
## Related content
8281

83-
- [Get started with Azure Synapse Link for Azure SQL Database](../connect-synapse-link-sql-database.md)
84-
- [Get started with Azure Synapse Link for SQL Server 2022](../connect-synapse-link-sql-server-2022.md)
85-
- [Known limitations and issues with Azure Synapse Link for SQL](../synapse-link-for-sql-known-issues.md)
82+
- [Get started with Azure Synapse Link for Azure SQL Database](../connect-synapse-link-sql-database.md)
83+
- [Get started with Azure Synapse Link for SQL Server 2022](../connect-synapse-link-sql-server-2022.md)
84+
- [Known limitations and issues with Azure Synapse Link for SQL](../synapse-link-for-sql-known-issues.md)

0 commit comments

Comments
 (0)