Merge branch 'master' of https://github.com/MicrosoftDocs/sql-docs-pr into us1612823a

Author: TimShererWithAquent

docs/2014/tools/configuration-manager/choosing-a-network-protocol.md

@@ -1,5 +1,6 @@
 ---
 title: "Choosing a Network Protocol | Microsoft Docs"
+description: Compare and contrast network protocols that are available for connecting to SQL Server Database Engine, such as shared memory, TCP/IP, and named pipes.
 ms.custom: ""
 ms.date: "06/13/2017"
 ms.prod: "sql-server-2014"

docs/2014/tools/configuration-manager/client-protocols-tcp-and-ip-properties-protocol-tab.md

@@ -1,5 +1,6 @@
 ---
 title: "Client Protocols - TCP and IP Properties (Protocol Tab) | Microsoft Docs"
+description: Learn how to specify TCP/IP options in Microsoft SQL Server Configuration Manager, such as the keep alive parameter and the default port number.
 ms.custom: ""
 ms.date: "06/13/2017"
 ms.prod: "sql-server-2014"

docs/2014/tools/configuration-manager/creating-a-valid-connection-string-using-named-pipes.md

@@ -1,5 +1,6 @@
 ---
 title: "Creating a Valid Connection String Using Named Pipes | Microsoft Docs"
+description: Learn how to create a valid connection string when using the named pipes protocol to connect to an instance of SQL Server. View examples of valid pipe names.
 ms.custom: ""
 ms.date: "06/13/2017"
 ms.prod: "sql-server-2014"

docs/connect/odbc/linux-mac/installing-the-microsoft-odbc-driver-for-sql-server.md

@@ -125,6 +125,8 @@ sudo yum install unixODBC-devel
 
 ```bash
 sudo su
+curl -O https://packages.microsoft.com/keys/microsoft.asc
+rpm --import microsoft.asc
 
 #Download appropriate package for the OS version
 #Choose only ONE of the following, corresponding to your OS version

docs/database-engine/configure-windows/affinity-mask-server-configuration-option.md

@@ -1,5 +1,6 @@
 ---
 title: "Common Criteria Compliance Enabled Configuration | Microsoft Docs"
+description: Learn which criteria the common criteria compliance option enables in SQL Server, and see how to comply with Common Criteria Evaluation Assurance Level 4+.
 ms.custom: ""
 ms.date: "08/21/2018"
 ms.prod: sql

docs/database-engine/configure-windows/common-criteria-compliance-enabled-server-configuration-option.md

@@ -17,7 +17,7 @@ ms.author: maghan
 # Configure the max worker threads Server Configuration Option
 [!INCLUDE[appliesto-ss-xxxx-xxxx-xxx-md](../../includes/appliesto-ss-xxxx-xxxx-xxx-md.md)]
 
-This topic describes how to configure the **max worker threads** server configuration option in [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] by using [!INCLUDE[ssManStudioFull](../../includes/ssmanstudiofull-md.md)] or [!INCLUDE[tsql](../../includes/tsql-md.md)]. The **max worker threads** option configures the number of worker threads that are available to [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] processes.
+This topic describes how to configure the **max worker threads** server configuration option in [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] by using [!INCLUDE[ssManStudioFull](../../includes/ssmanstudiofull-md.md)] or [!INCLUDE[tsql](../../includes/tsql-md.md)]. The **max worker threads** option configures the number of worker threads that are available [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)]-wide to process query requests, login, logout, and similar application requests.
 
 
 [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] uses the native thread services of the operating systems to ensure the following conditions:
@@ -34,9 +34,9 @@ The default value for **max worker threads** is 0. This enables [!INCLUDE[ssNoVe
 
 ###  <a name="Restrictions"></a> Limitations and Restrictions  
 
--   When the actual number of query requests is less than the amount set in **max worker threads**, one thread handles each query request. However, if the actual number of query requests exceeds the amount set in **max worker threads**, [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] pools the worker threads so that the next available worker thread can handle the request.
+-   The actual number of query requests can exceed the value set in **max worker threads** in which case  [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] pools the worker threads so that the next available worker thread can handle the request. A worker thread is assigned only to active requests and is released once the request is serviced. This happens even if the user session/connection on which the request was made remains open. 
 
--   The **max worker threads** server configuration option does not limit all threads that may be spawned in the system. Threads required for tasks such as Availability Groups, Service Broker, Lock Manager, or others are spawned outside this limit. If the number of threads configured is being exceeded, the following query will provide information about the system tasks that have spawned the additional threads.  
+-   The **max worker threads** server configuration option does not limit all threads that may be spawned inside the engine. System threads required for tasks such as LazyWriter, Checkpoint, Log Writer, Service Broker, Lock Manager, or others are spawned outside this limit. Availability Groups use some of the worker threads from within the **max worker thread limit** but also use system threads (see [Thread Usage by Availability Groups](../availability-groups/windows/prereqs-restrictions-recommendations-always-on-availability.md#ThreadUsage) ) If the number of threads configured is being exceeded, the following query will provide information about the system tasks that have spawned the additional threads.  
 
  ```sql  
  SELECT  s.session_id, r.command, r.status,  
@@ -56,11 +56,11 @@ The default value for **max worker threads** is 0. This enables [!INCLUDE[ssNoVe
 
 ###  <a name="Recommendations"></a> Recommendations  
 
--   This option is an advanced option and should be changed only by an experienced database administrator or certified [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] professional. If you suspect that there is a performance problem, it is probably not the availability of worker threads. The cause is more likely something like I/O that is causing the worker threads to wait. It is best to find the root cause of a performance issue before you change the max worker threads setting. For more information on assessing performance, see [Monitor and tune for performance](../../relational-databases/performance/monitor-and-tune-for-performance.md).
+-   This option is an advanced option and should be changed only by an experienced database administrator or certified [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] professional. If you suspect that there is a performance problem, it is probably not the availability of worker threads. The cause is more likely related to activies that occupy the worker threads and do not release them. Examples include long-running queries or bottlenecks on the system (I/O, blocking, latch waits, network waits) that cause long-waiting queries. It is best to find the root cause of a performance issue before you change the max worker threads setting. For more information on assessing performance, see [Monitor and tune for performance](../../relational-databases/performance/monitor-and-tune-for-performance.md).
 
 -   Thread pooling helps optimize performance when a large number of clients connect to the server. Usually, a separate operating system thread is created for each query request. However, with hundreds of connections to the server, using one thread per query request can consume large amounts of system resources. The **max worker threads** option enables [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] to create a pool of worker threads to service a larger number of query requests, which improves performance.  
 
--   The following table shows the automatically configured number of max worker threads for various combinations of CPUs, computer architecture, and versions of [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)], using the formula: ***Default Max Workers* + ((*logical CPUs* - 4) * *Workers per CPU*)**.  
+-   The following table shows the automatically configured number of max worker threads (when value is set to 0) based on various combinations of CPUs, computer architecture, and versions of [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)], using the formula: ***Default Max Workers* + ((*logical CPUs* - 4) * *Workers per CPU*)**.  
 
     |Number of CPUs|32-bit computer (up to [!INCLUDE[ssSQL14](../../includes/sssql14-md.md)])|64-bit computer (up to [!INCLUDE[ssSQL15](../../includes/sssql15-md.md)] SP1)|64-bit computer (starting with [!INCLUDE[ssSQL15](../../includes/sssql15-md.md)] SP2 and [!INCLUDE[ssSQL17](../../includes/sssql17-md.md)])|   
     |------------|------------|------------|------------|  

docs/database-engine/configure-windows/configure-the-max-worker-threads-server-configuration-option.md

@@ -1,5 +1,6 @@
 ---
 title: "Configure the remote data archive Server Configuration Option | Microsoft Docs"
+description: Learn how to use the remote data archive option in SQL Server to specify whether databases and tables on the server can be enabled for Stretch.
 ms.custom: ""
 ms.date: "03/02/2017"
 ms.prod: sql

docs/database-engine/configure-windows/configure-the-remote-data-archive-server-configuration-option.md

@@ -1,5 +1,6 @@
 ---
 title: "Connect to the Database Engine Using Extended Protection | Microsoft Docs"
+description: Learn how Extended Protection uses service binding and channel binding to help prevent authentication relay attacks. See how to enable this feature.
 ms.custom: ""
 ms.date: "05/21/2019"
 ms.prod: sql

docs/database-engine/configure-windows/connect-to-the-database-engine-using-extended-protection.md

@@ -29,8 +29,8 @@ SSL/TLS certificates are widely used to secure access to SQL Server. With earlie
 
 * Viewing and validating certificates installed in a SQL Server instance. 
 * Identifying which certificates may be close to expiring. 
-* Deploying certificates across Availability Group machines from the node holding the primary replica. 
-* Deploying certificates across machines participating in a Failover Cluster instance from the active node.
+* Deploying certificates across Always On Availability Group machines from the node holding the primary replica. 
+* Deploying certificates across machines participating in an Always On failover cluster instance from the active node.
 
 > [!NOTE]
 > You can use certificate management in SQL Server Configuration Manager with lower versions of SQL Server, starting with SQL Server 2008.
@@ -48,7 +48,7 @@ SSL/TLS certificates are widely used to secure access to SQL Server. With earlie
 5. Select **Next** to validate the certificate. If there are no errors, select **Next** to import the certificate to the local instance.  
 
 
-##  <a name="provision-failover-cluster-cert"></a> To install a certificate in a Failover Cluster configuration  
+##  <a name="provision-failover-cluster-cert"></a> To install a certificate in a failover cluster instance configuration  
 
 1. In SQL Server Configuration Manager, in the console pane, expand **SQL Server Network Configuration**.
 
@@ -60,7 +60,7 @@ SSL/TLS certificates are widely used to secure access to SQL Server. With earlie
 
 5. If installing for a single node, choose **Browse** and select certificate file. Then skip to step 8.
 
-6. If installing a certificate for each node, select **Next** to list possible owner nodes. Possible owners for the current SQL Server FCI are pre-selected.
+6. If installing a certificate for each node, select **Next** to list possible owner nodes. Possible owners for the current failover cluster instance are pre-selected.
 
 7. Choose **Next** to select the certificate to be imported.
 
@@ -69,9 +69,9 @@ SSL/TLS certificates are widely used to secure access to SQL Server. With earlie
 9. Select **Next** to import the selected certificates.
 
 > [!NOTE]
-> Complete these steps in the active node of the SQL Server Failover Cluster instance. User must have administrator permissions on all the cluster nodes.
+> Complete these steps in the active node of the Always On failover cluster instance. User must have administrator permissions on all the cluster nodes.
 
-##  <a name="provision-availability-group-cert"></a>To install a certificate in an Availability Group configuration  
+##  <a name="provision-availability-group-cert"></a>To install a certificate in an Always On Availability Group configuration  
 
 1. In SQL Server Configuration Manager, in the console pane, expand **SQL Server Network Configuration**.