Edited link feature best practices

MashaMSFT · MashaMSFT · commit fb6e3d62183a · 2022-03-10T13:52:51.000-08:00
diff --git a/articles/azure-sql/managed-instance/link-feature-best-practices.md b/articles/azure-sql/managed-instance/link-feature-best-practices.md
@@ -16,19 +16,22 @@ ms.date: 03/10/2022
 # Best practices with link feature for Azure SQL Managed Instance (preview)
 [!INCLUDE[appliesto-sqlmi](../includes/appliesto-sqlmi.md)]
 
-This article outlines best practices with using the link feature for Azure SQL Managed Instance. The link feature for Azure SQL Managed Instance connects your SQL Servers hosted anywhere to SQL Managed Instance, providing near real-time data replication to the cloud. 
+This article outlines best practices when using the link feature for Azure SQL Managed Instance. The link feature for Azure SQL Managed Instance connects your SQL Servers hosted anywhere to SQL Managed Instance, providing near real-time data replication to the cloud. 
 
 > [!NOTE]
 > The link feature for Azure SQL Managed Instance is currently in preview. 
 
-## Taking log backups regularly
+## Take log backups regularly
 
-The link feature replicates data using [Distributed availability groups](https://docs.microsoft.com/sql/database-engine/availability-groups/windows/distributed-availability-groups) concept based on SQL Server Always On availability groups technology stack. Data replication with distributed availability groups is based on replicating transaction log records. No transaction log records can be truncated from the database on primary instance until they're distributed to the database on secondary instance. In case that transaction log record distribution is slow or blocked due to network connection issue, the log file will keep growing. Growth speed depends on the intensity of workload and the network speed. If there's a prolonged network connection outage and heavy workload on primary instance, the log file may take all available storage space.
+The link feature replicates data using the [Distributed availability groups](https://docs.microsoft.com/sql/database-engine/availability-groups/windows/distributed-availability-groups) concept based the Always On availability groups technology stack. Data replication with distributed availability groups is based on replicating transaction log records. No transaction log records can be truncated from the database on the primary instance until they're replicated to the database on the secondary instance. If transaction log record replication is slow or blocked due to network connection issues, the log file keeps growing on the primary instance. Growth speed depends on the intensity of workload and the network speed. If there's a prolonged network connection outage and heavy workload on primary instance, the log file may take all available storage space.
 
-> [!IMPORTANT]
-> To minimize risk of running out of space on your primary instance due to log file growth, make sure to keep the usual log file size under control by taking database log backups regularly. By taking log backups regularly, you make your database more resilient to unplanned log growth events. Consider scheduling daily log backup tasks using SQL Server Agent job.
 
-You can use the following sample script for backing up log file. Replace the placeholders in the sample script with name of your database, path and name of the backup file, and the description, respectively:
+To minimize the risk of running out of space on your primary instance due to log file growth, make sure to take database log backups regularly. By taking log backups regularly, you make your database more resilient to unplanned log growth events. Consider scheduling daily log backup tasks using SQL Server Agent job.
+
+You can use a Transact-SQL (T-SQL) script to back up the log file, such as the sample provided in this section. Replace the placeholders in the sample script with name of your database, name and path of the backup file, and the description.
+
+To backup your transaction log, use the following sample Transact-SQL (T-SQL) script: 
+
 ```sql
 
 USE [<DatabaseName>]
@@ -48,19 +51,27 @@ NAME = N'<Description>', SKIP, NOREWIND, NOUNLOAD, COMPRESSION, STATS = 1
 END
 ```
 
-At any time you can execute the following command to check the log space used by your databases:
+
+Use the following Transact-SQL (T-SQL) command to check the log spaced used by your database: 
+
 ```sql
 DBCC SQLPERF(LOGSPACE); 
 ```
 
-The query output will look like in the example below for fictive database "tpcc":
+The query output looks like the following example below for sample database **tpcc**:
 
 :::image type="content" source="./media/link-feature-best-practices/database-log-file-size.png" alt-text="Screenshot with results of the command showing log file size and space used":::
 
-In the example, database has used 76% of the log  available, with absolute log file size of approximately 27 GB (27,971 MB). Thresholds for action may vary based on your workload, but its typically indication that log backup should be taken to truncate log file and free up some space. 
+In this example, the database has used 76% of the available log, with an absolute log file size of approximately 27 GB (27,971 MB). The thresholds for action may vary based on your workload, but its typically an indication that you should take a log backup to truncate log file and free up some space. 
+
+## Add start up trace flags
+
+There are two trace flags (`-T1800` and `-T9567`) that, when added as start up parameters, can optimize the performance of data replication through the link. See [Enable start up trace flags](managed-instance-link-preparation.md#enable-feature-startup-trace-flags) to learn more. 
 
 ## Next steps
 
+To get started with the link feature, [prepare your environment for replication](managed-instance-link-preparation.md). 
+
 For more information on the link feature, see the following articles:
 
 - [Managed Instance link – overview](link-feature.md).
diff --git a/articles/azure-sql/managed-instance/managed-instance-link-preparation.md b/articles/azure-sql/managed-instance/managed-instance-link-preparation.md
@@ -19,7 +19,8 @@ ms.date: 03/07/2022
 
 This article teaches you to prepare your environment for the [Managed Instance link feature](link-feature.md) so that you can replicate your databases from your instance of SQL Server to your instance of Azure SQL Managed Instance. 
 
-Managed Instance link is currently in public preview.
+> [!NOTE]
+> The link feature for Azure SQL Managed Instance is currently in preview. 
 
 ## Prerequisites 
 
@@ -82,7 +83,7 @@ If the availability groups feature is not enabled, follow these steps to enable
 
 1. Select **OK** on the dialog box to restart the SQL Server service.
 
-### Enable feature startup trace flags
+### Enable startup trace flags
 
 To optimize Managed Instance link performance, enabling trace flags `-T1800` and `-T9567` at startup is highly recommended: 
 
diff --git a/articles/azure-sql/managed-instance/managed-instance-link-use-ssms-to-failover-database.md b/articles/azure-sql/managed-instance/managed-instance-link-use-ssms-to-failover-database.md
@@ -23,7 +23,8 @@ Failing over your database from your SQL Server instance to your SQL Managed Ins
 
 Before failing over your database, make sure you've [prepared your environment](managed-instance-link-preparation.md) and [configured replication through the link feature](managed-instance-link-use-ssms-to-replicate-database.md). 
 
-Managed Instance link is currently in public preview.
+> [!NOTE]
+> The link feature for Azure SQL Managed Instance is currently in preview. 
 
 ## Prerequisites 
 
diff --git a/articles/azure-sql/managed-instance/managed-instance-link-use-ssms-to-replicate-database.md b/articles/azure-sql/managed-instance/managed-instance-link-use-ssms-to-replicate-database.md
@@ -21,7 +21,8 @@ This article teaches you to use the [Managed Instance link feature](link-feature
 
 Before configuring replication for your database through the link feature, make sure you've [prepared your environment](managed-instance-link-preparation.md). 
 
-Managed Instance link is currently in public preview.
+> [!NOTE]
+> The link feature for Azure SQL Managed Instance is currently in preview. 
 
 ## Prerequisites 
 
diff --git a/articles/azure-sql/toc.yml b/articles/azure-sql/toc.yml
@@ -1229,14 +1229,16 @@
       - name: Migrate TDE cert 
         href: managed-instance/tde-certificate-migrate.md
 
-    - name: Managed Instance link
+    - name: Managed Instance link feature
       items:
       - name: Prepare environment for link 
         href: managed-instance/managed-instance-link-preparation.md
       - name: Replicate databases in SSMS
         href: managed-instance/managed-instance-link-use-ssms-to-replicate-database.md
       - name: Failover databases in SSMS
         href: managed-instance/managed-instance-link-use-ssms-to-failover-database.md
+      - name: Best practices
+        href: managed-instance/link-feature-best-practices.md
 
     - name: Configure business continuity 
       items: 
