Merge pull request #216429 from im-microsoft/patch-1

Update faq.yml

Author: Court72

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

@@ -7,8 +7,9 @@ metadata:
   ms.topic: faq
   ms.subservice: synapse-link
   ms.custom: event-tier1-build-2022
-  ms.date: 05/13/2022
+  ms.date: 11/02/2022
   ms.author: yexu
+  ms.reviewer: wiassaf, imotiwala
 title: Azure Synapse Link for SQL FAQ
 summary: In this guide, you'll find the most frequently asked questions for Azure Synapse Link for SQL.
 
@@ -22,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 supports Azure SQL Database and SQL Server 2022 as the source stores only.
+          No, currently Azure Synapse Link for SQL only supports Azure SQL Database and SQL Server (starting with 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: |
@@ -97,3 +98,19 @@ sections:
           What data replication mechanism is used by Azure Synapse Link for SQL?
         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 to SQL Server?
+        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 DB?
+        answer: |
+          If the Azure Synapse workspace is removed, Azure SQL DB 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. 
+      - question: |
+          What is the impact when a user removes the Azure Synapse workspace that contains an Azure Synapse Link to SQL Server?
+        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.
+      - question: |
+          What is the impact when a user intentionally removes the Azure Synapse Link landing zone for Azure Synapse Link to SQL Server?
+        answer: | 
+          In SQL Server, the landing zone storage account is user managed. If the landing zone storage account is no longer accessible, and there will be 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).