Merge pull request #18225 from markingmyname/ghjan21

[Issues]  Issue-a-thon changes Jan 2021

Author: Court72

docs/database-engine/configure-windows/manage-certificates.md

@@ -1,11 +1,8 @@
 ---
-title: "Certificate Management (SQL Server Configuration Manager) | Microsoft Docs"
+title: Certificate Management (SQL Server Configuration Manager)
 description: Learn how to install certificates in various SQL Server configurations. Examples include single instances, failover clusters, and Always On availability groups.
-ms.custom: ""
-ms.date: "01/16/2019"
 ms.prod: sql
 ms.prod_service: high-availability
-ms.reviewer: ""
 ms.technology: configuration
 ms.topic: conceptual
 helpviewer_keywords: 
@@ -21,7 +18,11 @@ helpviewer_keywords:
 ms.assetid: e1e55519-97ec-4404-81ef-881da3b42006
 author: markingmyname
 ms.author: maghan
+ms.reviewer: ""
+ms.custom: ""
+ms.date: "01/12/2021"
 ---
+
 # Certificate Management (SQL Server Configuration Manager)
 
 This topic describes how to deploy and manage certificates across your SQL Server Always On Failover Cluster or Availability Group topology.
@@ -37,18 +38,29 @@ SSL/TLS certificates are widely used to secure access to SQL Server. With earlie
 > You can use certificate management in SQL Server Configuration Manager with lower versions of SQL Server, starting with SQL Server 2008.
 
 ##  <a name="provision-single-server-cert"></a> To install a certificate for a single SQL Server instance  
-  
+
+::: moniker range=">=sql-server-ver15"
 1. In SQL Server Configuration Manager, in the console pane, expand **SQL Server Network Configuration**.  
-  
+
 2. Right-click **Protocols for** *&lt;instance Name&gt;*, and then select **Properties**.  
-  
+
 3. Choose the **Certificate** tab, and then select **Import**.  
-  
+
 4. Select **Browse** and then select the certificate file.  
-  
+
 5. Select **Next** to validate the certificate. If there are no errors, select **Next** to import the certificate to the local instance.  
-  
- 
+::: moniker-end
+
+::: moniker range="<= sql-server-2017"
+1. In SQL Server Configuration Manager, in the console pane, expand **SQL Server Network Configuration**.  
+
+2. Right-click **Protocols for** *&lt;instance Name&gt;*, and then select **Properties**.  
+
+3. Select a certificate from the  **Certificate** drop-down menu, and then select **Apply**.  
+
+4. Select **OK**. 
+::: moniker-end
+
 ##  <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**.

docs/t-sql/functions/datediff-big-transact-sql.md

@@ -1,11 +1,8 @@
 ---
+title: DATEDIFF_BIG (Transact-SQL)
 description: "DATEDIFF_BIG (Transact-SQL)"
-title: "DATEDIFF_BIG (Transact-SQL) | Microsoft Docs"
-ms.custom: ""
-ms.date: "07/18/2019"
 ms.prod: sql
 ms.prod_service: "database-engine, sql-database"
-ms.reviewer: ""
 ms.technology: t-sql
 ms.topic: "language-reference"
 f1_keywords: 
@@ -21,7 +18,11 @@ helpviewer_keywords:
 ms.assetid: 19ac1693-3cfa-400d-bf83-20a9cb46599a
 author: cawrites
 ms.author: chadam
+ms.reviewer: ""
+ms.custom: ""
+ms.date: "01/12/2021"
 ---
+
 # DATEDIFF_BIG (Transact-SQL)
 
 [!INCLUDE [sqlserver2016-asdb-asdbmi](../../includes/applies-to-version/sqlserver2016-asdb-asdbmi.md)]
@@ -84,13 +85,13 @@ See *startdate*.
 Signed **bigint**  
 
 ## Return Value  
-Returns the **bigint** difference between the *startdate* and *enddate*, expressed in the coundary set by *datepart*.
+Returns the **bigint** difference between the *startdate* and *enddate*, expressed in the boundary set by *datepart*.
 
-For a return value out of range for **bigint** (-9,223,372,036,854,775,808 to 9,223,372,036,854,775,807), `DATEDIFF_BIG` returns an error. Unlike `DATEDIFF` which returns an **int** and therefore may overflow with a precision of **minute** or higher, `DATEDIFF_BIG` can only overflow if using **nanosecond** precision where the difference between *enddate* and *startdate* is more than 292 years, 3 months, 10 days, 23 hours, 47 minutes and 16.8547758 seconds.
+For a return value out of range for **bigint** (-9,223,372,036,854,775,808 to 9,223,372,036,854,775,807), `DATEDIFF_BIG` returns an error. Unlike  , which returns an **int** and therefore may overflow a **minute** or higher, `DATEDIFF_BIG` can only overflow if using **nanosecond** precision where the difference between *enddate* and *startdate* is more than 292 years, 3 months, 10 days, 23 hours, 47 minutes, and 16.8547758 seconds.
 
-If *startdate* and *enddate* are both assigned only a time value, and the *datepart* is not a time *datepart*, `DATEDIFF_BIG` returns 0.
+If *startdate* and *enddate* are both assigned only a time value, and the *datepart* isn't a time *datepart*, `DATEDIFF_BIG` returns 0.
 
-`DATEDIFF_BIG` does not use a time zone offset component of *startdate* or *enddate* to calculate the return value.
+`DATEDIFF_BIG` does use a time zone offset component of *startdate* or *enddate* to calculate the return value.
 
 For a **smalldatetime** value used for *startdate* or *enddate*, `DATEDIFF_BIG` always sets seconds and milliseconds to 0 in the return value because [smalldatetime](../../t-sql/data-types/smalldatetime-transact-sql.md) only has accuracy to the minute.
 
@@ -117,11 +118,11 @@ SELECT DATEDIFF_BIG(millisecond, '2005-12-31 23:59:59.9999999', '2006-01-01 00:0
 ## Remarks  
 Use `DATEDIFF_BIG` in the `SELECT <list>`, `WHERE`, `HAVING`, `GROUP BY` and `ORDER BY` clauses.
 
-`DATEDIFF_BIG` implicitly casts string literals as a **datetime2** type. This means that `DATEDIFF_BIG` does not support the format YDM when the date is passed as a string. You must explicitly cast the string to a **datetime** or **smalldatetime** type to use the YDM format.
+`DATEDIFF_BIG` implicitly casts string literals as a **datetime2** type. This means that `DATEDIFF_BIG` doesn't support the format YDM when the date is passed as a string. You must explicitly cast the string to a **datetime** or **smalldatetime** type to use the YDM format.
 
 Specifying `SET DATEFIRST` has no effect on `DATEDIFF_BIG`. `DATEDIFF_BIG` always uses Sunday as the first day of the week to ensure the function operates in a deterministic way.
 
-`DATEDIFF_BIG` may overflow with a precision of **nanosecond** if the difference between *enddate* and *startdate* returns a value that is out of range for **bigint**.
+`DATEDIFF_BIG` may overflow with a **nanosecond** if the difference between *enddate* and *startdate* returns a value that is out of range for **bigint**.
 
 ## Examples