20221108 1457 edit pass

WilliamDAssafMSFT · WilliamDAssafMSFT · commit 84c9ffdbc9b7 · 2022-11-08T15:01:13.000-08:00
diff --git a/articles/synapse-analytics/synapse-link/faq.yml b/articles/synapse-analytics/synapse-link/faq.yml
@@ -7,7 +7,7 @@ metadata:
   ms.topic: faq
   ms.subservice: synapse-link
   ms.custom: event-tier1-build-2022
-  ms.date: 11/02/2022
+  ms.date: 11/08/2022
   ms.author: yexu
   ms.reviewer: wiassaf, imotiwala
 title: Azure Synapse Link for SQL FAQ
@@ -27,12 +27,12 @@ sections:
       - question: |
           Do I need to stop the link connection when I want to add or remove tables to be replicated?
         answer: |
-          No, you can add or remove tables when the link connection is running. The tables which are removed will stop being replicated automatically. The newly added tables will start from initial load with full snapshot and then do incremental synchronization. The rest of the tables in the same link connection will not be impacted.
+          No, you can add or remove tables when the link connection is running. The tables that are removed will stop being replicated automatically. The newly added tables will start from initial load with full snapshot and then do incremental synchronization. The rest of the tables in the same link connection will not be impacted.
       - question: |
-          My destination tables exist in the target Synapse dedicated SQL pool which causes my link connection to fail to start. What should I do?
+          My destination tables exist in the target dedicated SQL pool, which causes my link connection to fail to start. What should I do?
         answer: |
           You should remove the destination tables before starting a link connection. You can do that by either manually removing the tables from Synapse dedicated SQL pool or checking “Drop and recreate table on target” in the link connection to let it automatically drop existing tables on the Synapse dedicated SQL pool every time when starts.
-          :::image type="content" source="../media/sql-synapse-link-overview/drop-recreate-target-table.png" lightbox="../media/sql-synapse-link-overview/drop-recreate-target-table.png" alt-text="Shows a screenshot of the Drop and Recreate Target Table option for Synapse Link for SQL Server.":::
+          :::image type="content" source="../media/sql-synapse-link-overview/drop-recreate-target-table.png" lightbox="../media/sql-synapse-link-overview/drop-recreate-target-table.png" alt-text="Shows a screenshot of the Drop and Recreate Target Table option for Azure Synapse Link for SQL Server.":::
       - question: |
           What happens on my running link connection if the table columns have been added or dropped from our source stores?
         answer: |
@@ -42,7 +42,7 @@ sections:
         answer: |
           No, you cannot. Pausing and resuming a link connection will be coming soon.
       - question: |
-          Can I select managed virtual network in Synapse workspace with Synapse managed private endpoints which allow the link connection to privately connect to the source database?
+          Can I select managed virtual network in Synapse workspace with Synapse managed private endpoints, which allow the link connection to privately connect to the source database?
         answer: |
           Yes, you can. Similar like all the workloads in Synapse. You can enable Synapse link for SQL in Azure Synapse-managed virtual network to replicate data from SQL to Synapse in a secure manner.  You can protect against data exfiltration by allowing outbound connectivity from the managed virtual network only to approved targets using managed private endpoints.
       - question: |
@@ -57,15 +57,15 @@ sections:
       - question: |
           How should I select the structure type of my destination table in the Synapse dedicated SQL pool?
         answer: |
-          You can refer to [Indexing tables - Azure Synapse Analytics | Microsoft Docs](../sql-data-warehouse/sql-data-warehouse-tables-index.md) to understand the three options for table structure type. When clustered columnstore index is chosen, data type with max length (eg. VARCHAR(MAX)) is not supported.
+          You can refer to [Indexing tables - Azure Synapse Analytics | Microsoft Docs](../sql-data-warehouse/sql-data-warehouse-tables-index.md) to understand the three options for table structure type. When clustered columnstore index is chosen, data type with max length (for example, VARCHAR(MAX)) is not supported.
       - question: |
           Do I need to clean up data in the landing zone?
         answer: |
           No. There is a background thread that removes committed files after around 24 hours as long as the link is continuously running. When the link is stopped then the entire landing zone folder is removed.
       - question: |
-          Which regions does Azure Synapse Link for SQL available in?
+          In which regions is Azure Synapse Link for SQL available?
         answer: |
-          Azure Synapse Link for SQL is available in all regions where [Azure Synapse Workspace is currently available] (https://azure.microsoft.com/en-us/explore/global-infrastructure/products-by-region/?products=synapse-analytics&rar=true&regions=all)
+          Azure Synapse Link for SQL is available in all regions where [Azure Synapse Workspace is currently available](https://azure.microsoft.com/explore/global-infrastructure/products-by-region/?products=synapse-analytics&rar=true&regions=all).
       - question: |
           Where is my landing zone located?
         answer: |
@@ -97,7 +97,7 @@ sections:
       - question: |
           There is a documented limit of 7,500 bytes per row for Azure Synapse Link for SQL. What if I have larger data rows in my source database?
         answer: |
-          This restriction is for on-page data only. For off-page data, the only thing that counts against the 7,500 byte limit is the 24 byte pointer to the off-page data.
+          This restriction is for on-page data only. For off-page data, the only thing that counts against the 7,500-byte limit is the 24-byte pointer to the off-page data.
       - question: |
           What data replication mechanism is used by Azure Synapse Link for SQL?
         answer: |
diff --git a/articles/synapse-analytics/synapse-link/synapse-link-for-sql-known-issues.md b/articles/synapse-analytics/synapse-link/synapse-link-for-sql-known-issues.md
@@ -30,7 +30,7 @@ This is the list of known limitations for Azure Synapse Link for SQL.
 * 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.
 * 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 log in, Azure Synapse link for SQL will run 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.
+* When a database owner doesn't have a mapped log in, Azure Synapse Link for SQL will run 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.
 * If the source table contains computed columns or columns with data types that aren't supported by Azure Synapse Analytics dedicated SQL pools, these columns won't be replicated to Azure Synapse Analytics.  Unsupported columns include:
   * image
   * text
@@ -60,17 +60,17 @@ This is the list of known limitations for Azure Synapse Link for SQL.
 * System tables can't be replicated.
 * The security configuration from the source database will **NOT** be reflected in the target dedicated SQL pool.
 * Enabling Azure Synapse Link for SQL will create a new schema called `changefeed`. Don't use this schema, as it is reserved for system use.
-* Azure Synapse Link for SQL will **NOT** work and can't be enabled if your database contains a schema or user named "changefeed".
-* Source tables with collations that are unsupported by Synapse SQL dedicated pool, such as UTF8 and certain Japanese collations, can’t be replicated. Here's the [supported collations in Synapse SQL Pool](../sql/reference-collation-types.md).
-* Single row updates (including off-page storage) of > 370MB are not supported.
+* Azure Synapse Link for SQL will **NOT** work and can't be enabled if your database contains a schema or user named `changefeed`.
+* Source tables with collations that are unsupported by Synapse SQL dedicated pool, such as UTF8 and certain Japanese collations, can't be replicated. Here's the [supported collations in Synapse SQL Pool](../sql/reference-collation-types.md).
+* Single row updates (including off-page storage) of > 370 MB are not supported.
 
 ### Azure SQL DB only
 * Azure Synapse Link for SQL isn't supported on Free, Basic or Standard tier with fewer than 100 DTUs.
 * Azure Synapse Link for SQL isn't supported on SQL Managed Instances.
 * Service principal isn't supported for authenticating to source Azure SQL DB, so when creating Azure SQL DB linked Service, choose SQL authentication, user-assigned managed identity (UAMI) or service assigned managed Identity (SAMI).
 * If the Azure SQL Database logical server has both a SAMI and UAMI configured, Azure Synapse Link will use SAMI. 
 * Azure Synapse Link can't be enabled on the secondary database once a GeoDR failover has happened if the secondary database has a different name from the primary database.
-* If you enabled Azure Synapse Link for SQL on your database as an Microsoft Azure Active Directory (Azure AD) user, Point-in-time restore (PITR) will fail. PITR will only work when you enable Azure Synapse Link for SQL on your database as a SQL user.
+* If you enabled Azure Synapse Link for SQL on your database as a Microsoft Azure Active Directory (Azure AD) user, Point-in-time restore (PITR) will fail. PITR will only work when you enable Azure Synapse Link for SQL on your database as a SQL user.
 * If you create a database as an Azure AD user and enable Azure Synapse Link for SQL, a SQL authentication user (for example, even sysadmin role) won't be able to disable/make changes to Azure Synapse Link for SQL artifacts.  However, another Azure AD user will be able to enable/disable Azure Synapse Link for SQL on the same database. Similarly, if you create a database as an SQL authentication user, enabling/disabling Azure Synapse Link for SQL as an Azure AD user won't work.
 * When enabling Azure Synapse Link for SQL on your Azure SQL Database, you should ensure that aggressive log truncation is disabled.
 
@@ -84,8 +84,10 @@ This is the list of known limitations for Azure Synapse Link for SQL.
 > 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 may encounter transaction log full issues. 
 
 ## Known issues
-### Deleting an Azure Synapse Analytics workspace with a running link could cause log in source database to fill
-* Applies To - Azure SQL Database and SQL Server 2022
+
+### Deleting an Azure Synapse Analytics workspace with a running link could cause the transaction log in the source database to fill
+
+* Applies To - Azure Synapse Link for Azure SQL Database and SQL Server 2022
 * Issue - When you delete an Azure Synapse Analytics workspace it is possible that running links might not be stopped, which will cause the source database to think that the link is still operational and could lead to the log filling and not being truncated.
 * Resolution - There are two possible resolutions to this situation:
 1. Stop any running links prior to deleting the Azure Synapse Analytics workspace.
@@ -104,15 +106,17 @@ This is the list of known limitations for Azure Synapse Link for SQL.
         ```sql
         EXEC sys.sp_change_feed_disable_db
 
-### Trying to re-enable change feed on a table for that was recently disabled table will show an error. This is an uncommon behavior
-* Applies To - Azure SQL Database and SQL Server 2022
-* Issue - When you try to enable a table which has been recently disabled with its metadata not yet been cleaned up and state marked as DISABLED, an error will be thrown stating "A table can only be enabled once among all table groups"
+### Trying to re-enable change feed on a table for that was recently disabled table will show an error. This is an uncommon behavior.
+
+* Applies To - Azure Synapse Link for Azure SQL Database and SQL Server 2022
+* Issue - When you try to enable a table that has been recently disabled with its metadata not yet been cleaned up and state marked as DISABLED, an error will be thrown stating "A table can only be enabled once among all table groups".
 * Resolution - Wait for sometime for the disabled table system procedure to complete and then try to re-enable the table again.
 
-### Attempt to enable Synapse Link on an imported database using SSDT, SQLPackage for Import/Export and Extract/Deploy operations causes Synapse Link enablement to fail
-* Applies To - Azure SQL Database and SQL Server 2022
-* Issue - For SQL databases enabled with Synapse Link, when you use SSDT Import/Export and Extract/Deploy operations to import/setup a new database, the "changefeed" schema and user do not get excluded in the new database. On attempting to enable Synapse Link on the imported/deployed database, the system stored procedure sys.sp_change_feed_enable_db fails as the "changefeed" user and schema already exists. This issue will also be encountered if you have a user or schema named "changefeed" that is not related to Synapse Link changefeed capability.
-* Resolution - Manually drop the empty changefeed schema and user for Synapse Link to be enabled successfully on the imported/deployed database. **If you have defined a custom schema or user named "changefeed" in your database that is not related to Synapse Link and you do not intend to use Azure Synapse Link for SQL, please do NOT drop your "changefeed" schema or user to avoid any potential data loss**
+### Attempt to enable Synapse Link on database imported using SSDT, SQLPackage for Import/Export and Extract/Deploy operations 
+
+* Applies To - Azure Synapse Link for Azure SQL Database and SQL Server 2022
+* Issue - For SQL databases enabled with Azure Synapse Link, when you use SSDT Import/Export and Extract/Deploy operations to import/setup a new database, the `changefeed` schema and user do not get excluded in the new database. On attempting to enable Synapse Link on the imported/deployed database, the system stored procedure sys.sp_change_feed_enable_db fails as the `changefeed` user and schema already exists. This issue will also be encountered if you have a user or schema named `changefeed` that is not related to Synapse Link change feed capability.
+* Resolution - Manually drop the empty `changefeed` schema and `changefeed` user. Then, Synapse Link can be enabled successfully on the imported/deployed database. If you have defined a custom schema or user named `changefeed` in your database that is not related to Azure Synapse Link, and you do not intend to use Azure Synapse Link for SQL, it is not necessary to drop your `changefeed` schema or user.
 
 ## Next steps
 
