Merge pull request #23843 from MashaMSFT/202208_pubprs

combining a few public PRs

Author: Court72

azure-sql/includes/virtual-machines-sql-server-akv-next-steps.md

@@ -5,8 +5,6 @@ ms.date: 10/26/2018
 ms.service: virtual-machines-sql
 ms.topic: include
 ---
-## Next steps
-
 After enabling Azure Key Vault Integration, you can enable SQL Server encryption on your SQL VM. First, you will need to create an asymmetric key inside your key vault and a symmetric key within SQL Server on your VM. Then, you will be able to execute T-SQL statements to enable encryption for your databases and backups.
 
 There are several forms of encryption you can take advantage of:

azure-sql/virtual-machines/windows/azure-key-vault-integration-configure.md

@@ -46,6 +46,8 @@ For a detailed walkthrough of provisioning, see [Provision a SQL virtual machine
 
 For existing SQL virtual machines, open your [SQL virtual machines resource](manage-sql-vm-portal.md#access-the-resource) and select **Security** under **Settings**. Select **Enable** to enable Azure Key Vault integration. 
 
+The following screenshot shows how to enable Azure Key Vault in the portal for an existing SQL Server VM (this SQL Server instance uses a non-default port 1401): 
+
 ![SQL Key Vault integration for existing VMs](./media/azure-key-vault-integration-configure/azure-sql-rm-akv-existing-vms.png)
 
 When you're finished, select the **Apply** button on the bottom of the **Security** page to save your changes.
@@ -54,3 +56,7 @@ When you're finished, select the **Apply** button on the bottom of the **Securit
 > The credential name we created here will be mapped to a SQL login later. This allows the SQL login to access the key vault. 
 
 [!INCLUDE [Key Vault integration next steps](../../includes/virtual-machines-sql-server-akv-next-steps.md)]
+
+## Next steps
+
+For more security information, review [Security considerations for SQL Server on Azure VMs](security-considerations-best-practices.md). 

docs/database-engine/availability-groups/windows/overview-of-always-on-availability-groups-sql-server.md

@@ -46,7 +46,7 @@ helpviewer_keywords:
 > [!NOTE]  
 >  For information about the relationship of SQL Server Always On components to the WSFC cluster, see [Windows Server Failover Clustering (WSFC) with SQL Server](../../../sql-server/failover-clusters/windows/windows-server-failover-clustering-wsfc-with-sql-server.md).  
   
- The following illustration shows an availability group that contains one primary replica and four secondary replicas. Up to eight secondary replicas are supported, including one primary replica and two synchronous-commit secondary replicas.  
+ The following illustration shows an availability group that contains one primary replica and four secondary replicas. Up to eight secondary replicas are supported, including one primary replica and four synchronous-commit secondary replicas.  
 
  ![Availability group with five replicas](../../../database-engine/availability-groups/windows/media/aoag-agintrofigure.gif "Availability group with five replicas")  
 
@@ -178,4 +178,4 @@ The availability mode is a property of each availability replica. The availabili
 ## Next steps
 
 - [Getting Started with Always On Availability Groups](getting-started-with-always-on-availability-groups-sql-server.md)
-- [How-to: Administration of an availability group](administration-of-an-availability-group-sql-server.md)
+- [How-to: Administration of an availability group](administration-of-an-availability-group-sql-server.md)

docs/database-engine/availability-groups/windows/sql-server-always-on-database-health-detection-failover-option.md

@@ -17,12 +17,12 @@ helpviewer_keywords:
 ---
 # Availability group database level health detection failover option
 [!INCLUDE [SQL Server](../../../includes/applies-to-version/sqlserver.md)]
-Starting in SQL Server 2016, database level health detection (DB_FAILOVER) option is available when configuring an Always On availability group. The database level health detection notices when a database is no longer in the online status, when something goes wrong, and will trigger the automatic failover of the availability group.
+Starting in SQL Server 2016, database level health detection (DB_FAILOVER) option is available when configuring an Always On availability group. The database level health detection notices when a database is no longer in the online status, when something goes wrong, and will trigger the automatic failover of the availability group. Examples that may trigger the health detection include database in suspect mode, database is offline, database in recovery (failed to recover). For more information see [State column in sys.databases](../../../relational-databases/system-catalog-views/sys-databases-transact-sql.md).
 
 The database level health detection is enabled for the availability group as a whole, therefore database level health detection monitors every database in the availability group. It cannot be enabled selectively for specific databases in the availability group.
 
 ## Benefits of database level health detection option
----
+
 The availability group database level health detection option is widely recommended as a good option to help guarantee the high availability for your databases. You should consider turning it on for all availability groups. If your application depends on several databases to be highly available, group them into an availability group with the database health option turned on.
 
 For example, with database level health detection option on, if SQL Server was unable to write to the transaction log file for one of the databases, the status of that database would change to indicate failure, and the availability group would soon fail over, and your application could reconnect and continue working with minimal interruption once the databases are online again.
@@ -65,11 +65,11 @@ There are several easy ways to enable database level health detection setting:
 
 ### Caveats
 
-It is important to note that the Database Level Heath Detection option currently does not cause SQL Server to monitor disk uptime and SQL Server does not directly monitor database file availability. Should a disk drive fail or become unavailable, that alone will not necessarily trigger the availability group to automatically failover.
+It is important to note that the Database Level Heath Detection option currently does not cause SQL Server to monitor disk uptime and SQL Server does not directly monitor database file availability. Should a disk drive fail or become unavailable, that alone will not necessarily trigger the availability group to automatically fail over.
 
-As an example, when a database is idle with no active transactions, and with no physical writes occurring, should some of the database files become inaccessible, SQL Server may not do any read or write IO to the files, and may not change the status for that database immediately, so no failover would be triggered. Later, when a database checkpoint occurs, or a physical read or write occurs for fulfilling a query, then SQL Server may then notice the file issue, and react by changing the database status, and subsequently the availability group with database level health detection set on would failover due to the database health change.
+As an example, when a database is idle with no active transactions, and with no physical writes occurring, should some of the database files become inaccessible, SQL Server may not do any read or write IO to the files, and may not change the status for that database immediately, so no failover would be triggered. Later, when a database checkpoint occurs, or a physical read or write occurs for fulfilling a query, then SQL Server may then notice the file issue, and react by changing the database status, and subsequently the availability group with database level health detection set on would fail over due to the database health change.
 
-As another example, when the SQL Server database engine needs to read a data page to fulfill a query, if the data page is cached in the buffer pool memory, then no disk read with physical access may be required to fulfill the query request. Therefore, a missing or unavailable data file may not immediately trigger an automatic failover even when database health option is enabled, since database status is not immediately.
+As another example, when the SQL Server database engine needs to read a data page to fulfill a query, if the data page is cached in the buffer pool memory, then no disk read with physical access may be required to fulfill the query request. Therefore, a missing or unavailable data file may not immediately trigger an automatic failover even when database health option is enabled, since database status is not immediately updated.
 
 
 ## Database failover is separate from flexible failover policy
@@ -153,7 +153,7 @@ Explanation of the fields:
 |database_name |The name of the database reporting the fault.|
 |database_replica_id |The ID of the availability replica database.|
 |failover_ready_replicas |The number of automatic failover secondary replicas that are synchronized.|
-|fault_type  | The fault id reported. Possible values:  <br/> 0 - NONE <br/>1 - Unknown<br/>2 - Shutdown|
+|fault_type  | The fault ID reported. Possible values:  <br/> 0 - NONE <br/>1 - Unknown<br/>2 - Shutdown|
 |is_critical | This  value should always return true for the XEvent as of SQL Server 2016.|
 
 
@@ -182,4 +182,4 @@ In this example output, the fault_type shows that a critical event happened on t
 
 * [Enhance Always On Failover Policy to Test SQL Server Database Data and Log Drives](/archive/blogs/alwaysonpro/enhance-alwayson-failover-policy-to-test-sql-server-database-data-and-log-drives)
 
-* [Extended Events](../../../relational-databases/extended-events/extended-events.md)
+* [Extended Events](../../../relational-databases/extended-events/extended-events.md)

docs/linux/sql-server-linux-change-repo.md

@@ -23,7 +23,7 @@ This article describes how to configure the correct repository for [!INCLUDE [ss
 ::: zone-end
 
 ::: zone pivot="ld2-ubuntu"
-This article describes how to configure the correct repository for [!INCLUDE [sssql17-md](../includes/sssql17-md.md)] and [!INCLUDE [sssql19-md](../includes/sssql19-md.md)] installations and upgrades on Linux. At the top, your current selection is **Ubuntu**.
+This article describes how to configure the correct repository for [!INCLUDE [sssql17-md](../includes/sssql17-md.md)] and [!INCLUDE [sssql19-md](../includes/sssql19-md.md)] installations and upgrades on Linux. At the top, your current selection is **Ubuntu**.   
 ::: zone-end
 
 > [!TIP]  

docs/sql-server/failover-clusters/windows/wsfc-disaster-recovery-through-forced-quorum-sql-server.md

@@ -37,7 +37,7 @@ ms.author: mathoma
 > [!WARNING]  
 >  The user should be well-informed on the concepts and interactions of Windows Server Failover Clustering, WSFC Quorum Models, [!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)], and the environment's specific deployment configuration.  
 >   
->  For more information, see:  [Windows Server Failover Clustering (WSFC) with SQL Server](https://msdn.microsoft.com/library/hh270278\(v=SQL.110\).aspx), [WSFC Quorum Modes and Voting Configuration (SQL Server)](https://msdn.microsoft.com/library/hh270280\(v=SQL.110\).aspx)  
+>  For more information, see:  [Windows Server Failover Clustering (WSFC) with SQL Server](windows-server-failover-clustering-wsfc-with-sql-server.md), [WSFC Quorum Modes and Voting Configuration (SQL Server)](wsfc-quorum-modes-and-voting-configuration-sql-server.md)  
   
 ###  <a name="Security"></a> Security  
  The user must be a domain account that is member of the local Administrators group on each node of the WSFC cluster.