Merge pull request #6037 from MicrosoftDocs/FromPublicRepo

Confirm merge from FromPublicRepo to master to sync with https://github.com/MicrosoftDocs/sql-docs (branch live)

Author: huypub

docs/database-engine/availability-groups/windows/always-on-policies-for-operational-issues-always-on-availability.md

@@ -99,7 +99,7 @@ manager: craigg
 
  A user-defined policy can use any of the available PBM facets, including those used by the Always On predefined policies (see [Predefined Policies and Issues](#Always OnPBM), earlier in this topic). The Server facet provides the following properties for monitoring [!INCLUDE[ssHADR](../../../includes/sshadr-md.md)] health: (**IsHadrEnabled** and **HadrManagerStatus**). The Server facet also provides properties the following policies for monitoring the WSFC cluster configuration: **ClusterQuorumType**, and **ClusterQuorumState**.  
 
- For more information, see [The Always On Health Model Part 2 -- Extending the Health Model](http://blogs.msdn.com/b/sqlAlways On/archive/2012/02/13/extending-the-Always On-health-model.aspx) (a SQL Server Always On Team blog).  
+ For more information, see [The Always On Health Model Part 2 -- Extending the Health Model](https://blogs.msdn.microsoft.com/sqlalwayson/2012/02/13/the-alwayson-health-model-part-2-extending-the-health-model/) (a SQL Server Always On Team blog).  
 
 ##  <a name="RelatedTasks"></a> Related Tasks  
 
@@ -117,9 +117,9 @@ manager: craigg
 
 ##  <a name="RelatedContent"></a> Related Content  
 
--   [The Always On Health Model Part 1 -- Health Model Architecture](http://blogs.msdn.com/b/sqlAlways On/archive/2012/02/13/extending-the-Always On-health-model.aspx)  
+-   [The Always On Health Model Part 1 -- Health Model Architecture](https://blogs.msdn.microsoft.com/sqlalwayson/2012/02/08/the-alwayson-health-model-part-1-health-model-architecture/)  
 
--   [The Always On Health Model Part 2 -- Extending the Health Model](http://blogs.msdn.com/b/sqlAlways On/archive/2012/02/13/extending-the-Always On-health-model.aspx)  
+-   [The Always On Health Model Part 2 -- Extending the Health Model](https://blogs.msdn.microsoft.com/sqlalwayson/2012/02/13/the-alwayson-health-model-part-2-extending-the-health-model/)  
 
 -   [Microsoft SQL Server Always On Solutions Guide for High Availability and Disaster Recovery](http://go.microsoft.com/fwlink/?LinkId=227600)  
 

docs/relational-databases/databases/attach-a-database.md

@@ -159,7 +159,7 @@ We don't recommend using detach and attach for Backup and Recovery. There are no
   
 ## See Also  
  [CREATE DATABASE (SQL Server Transact-SQL)](../../t-sql/statements/create-database-sql-server-transact-sql.md) 
- <br>[Manage metadata when making a database available on another server](/manage-metadata-when-making-a-database-available-on-another-server.md)  
+ <br>[Manage metadata when making a database available on another server](manage-metadata-when-making-a-database-available-on-another-server.md)  
  [Detach a Database](../../relational-databases/databases/detach-a-database.md)  
   
   

docs/relational-databases/databases/rename-a-database.md

@@ -1,4 +1,4 @@
----
+---
 title: "Rename a Database | Microsoft Docs"
 ms.custom: ""
 ms.date: "11/20/2017"
@@ -42,7 +42,7 @@ monikerRange: "= azuresqldb-current || >= sql-server-2016 || = sqlallproducts-al
 -   **Follow Up:**  [After renaming a database](#FollowUp)  
 
 > [!NOTE]
-> To rename a database in Azure SQL Database, use the [ALTER DATABASE (Azure SQL Database)](../../t-sql/statements/alter-database-azure-sql-database.md) statement. To rename a database in Azure SQL Data Warehouse or Parallel Data Warehouse, use the [RENAME (Transact-SQL)](/t-sql/statements/rename-transact-sql) statement.
+> To rename a database in Azure SQL Database, use the [ALTER DATABASE (Azure SQL Database)](../../t-sql/statements/alter-database-azure-sql-database.md) statement. To rename a database in Azure SQL Data Warehouse or Parallel Data Warehouse, use the [RENAME (Transact-SQL)](../../t-sql/statements/rename-transact-sql.md) statement.
   
 ##  <a name="BeforeYouBegin"></a> Before You Begin  
 

docs/relational-databases/databases/tempdb-database.md

@@ -1,4 +1,4 @@
----
+---
 title: "tempdb Database | Microsoft Docs"
 description: This topic provides details regarding the configuration and use of the tempdb database in SQL Server and Azure SQL Database
 ms.custom: "P360"
@@ -130,7 +130,7 @@ Operations within **tempdb** are minimally logged so that transactions can be ro
 
 ### tempdb sizes for vCore-based service tiers
 
-See vCore-based resource limits](https://review.docs.microsoft.com/azure/sql-database/sql-database-vcore-resource-limits)
+See [vCore-based resource limits](https://docs.microsoft.com/azure/sql-database/sql-database-vcore-resource-limits)
 
 ## Restrictions  
  The following operations cannot be performed on the **tempdb** database:  

docs/relational-databases/security/encryption/rotate-always-encrypted-keys-using-powershell.md

@@ -1,4 +1,4 @@
----
+---
 title: "Rotate Always Encrypted Keys using PowerShell | Microsoft Docs"
 ms.custom: ""
 ms.date: "05/17/2017"
@@ -308,7 +308,7 @@ You can rotate a column encryption key using an offline or an online approach. T
 |Step 3. Authenticate to Azure, if your column master key (protecting the column encryption key, to be rotated), is stored in Azure Key Vault. | [Add-SqlAzureAuthenticationContext](https://docs.microsoft.com/powershell/sqlserver/sqlserver/vlatest/add-sqlazureauthenticationcontext) | Yes | No
 |Step 4. Generate a new column encryption key, encrypt it with the column master key and create column encryption key metadata in the database.  | [New-SqlColumnEncryptionKey](https://docs.microsoft.com/powershell/sqlserver/sqlserver/vlatest/new-sqlcolumnencryptionkey)<br><br>**Note:** Use a variation of the cmdlet that internally generates and encrypts a column encryption key.<br>Under the covers this cmdlet issues the [CREATE COLUMN ENCRYPTION KEY (Transact-SQL)](../../../t-sql/statements/create-column-encryption-key-transact-sql.md) statement to create the key metadata. | Yes | Yes
 |Step 5. Find all columns encrypted with the old column encryption key. | [SQL Server Management Objects (SMO) Programming Guide](../../../relational-databases/server-management-objects-smo/sql-server-management-objects-smo-programming-guide.md) | No | Yes
-|Step 6. Create a *SqlColumnEncryptionSettings* object for each impacted column.  SqlColumnMasterKeySettings is an object that exists in memory (in PowerShell). It specifies the target encryption scheme for a column. In this case, the object should specify the impacted column should be encrypted using the new column encryption key. | [New-SqlColumnEncryptionSettings](https://docs.microsoft.com/powershell/sqlserver/sqlserver/vlatest/new-sqlcolumnencryptionkeysettings) | No | No
+|Step 6. Create a *SqlColumnEncryptionSettings* object for each impacted column.  SqlColumnMasterKeySettings is an object that exists in memory (in PowerShell). It specifies the target encryption scheme for a column. In this case, the object should specify the impacted column should be encrypted using the new column encryption key. | [New-SqlColumnEncryptionSettings](https://docs.microsoft.com/powershell/sqlserver/sqlserver/vlatest/new-sqlcolumnencryptionsettings) | No | No
 |Step 7. Re-encrypt the columns, identified in step 5, using the new column encryption key. | [Set-SqlColumnEncryption](https://docs.microsoft.com/powershell/sqlserver/sqlserver/vlatest/set-sqlcolumnencryption)<br><br>**Note:** This step may take a long time. Your applications mill not be able to access the tables through the entire operation or a portion of it, depending on the approach (online vs. offline), you select. | Yes | Yes
 |Step 8. Remove the metadata for the old column encryption key. | [Remove-SqlColumnEncryptionKey](https://docs.microsoft.com/powershell/sqlserver/sqlserver/vlatest/remove-sqlcolumnencryptionkey) | No | Yes
 

docs/relational-databases/system-stored-procedures/xp-logevent-transact-sql.md

@@ -65,7 +65,7 @@ xp_logevent { error_number , 'message' } [ , 'severity' ]
  The following example logs the message, with variables passed to the message in the Windows Event Viewer.  
 
 ```  
-DECLARE @@TABNAME varchar(30, @@USERNAME varchar(30),DECLARE @@MESSAGE varchar(255);  
+DECLARE @@TABNAME varchar(30), @@USERNAME varchar(30),DECLARE @@MESSAGE varchar(255);  
 SET @@TABNAME = 'customers';  
 SET @@USERNAME = USER_NAME();  
 SELECT @@MESSAGE = 'The table ' + @@TABNAME + ' is not owned by the user   

docs/sql-operations-studio/tutorial-backup-restore-sql-server.md

@@ -72,7 +72,7 @@ After clicking **Backup**, the **Backup database** dialog disappears and the bac
 
 4. Click **Restore**
 
-5. To view the status of the restore operation, click **CTRL+T** to open the **Task History** sidebar.
+5. To view the status of the restore operation, press **CTRL+T** to open the **Task History** sidebar.
 
    ![restore](./media/tutorial-backup-restore-sql-server/task-history-restore.png)
 

docs/t-sql/data-types/TOC.md

@@ -3,8 +3,7 @@
 # [Conversion](data-type-conversion-database-engine.md)  
 # [Precedence](data-type-precedence-transact-sql.md)  
 # [Synonyms](data-type-synonyms-transact-sql.md)  
-# [Precision, Scale, and Length](precision-scale-and-length-transact-sql.md)  
-# [bit](bit-transact-sql.md)  
+# [Precision, Scale, and Length](precision-scale-and-length-transact-sql.md)    
 # [cursor](cursor-transact-sql.md)  
 # [Date and time](date-and-time-types.md)  
 ## [date](date-transact-sql.md)  
@@ -27,6 +26,7 @@
 ## [Write (Database Engine)](write-database-engine.md)  
 
 # [Numeric](numeric-types.md)  
+## [bit](bit-transact-sql.md)
 ## [decimal and numeric](decimal-and-numeric-transact-sql.md)  
 ## [float and real](float-and-real-transact-sql.md)  
 ## [int, bigint, smallint, and tinyint](int-bigint-smallint-and-tinyint-transact-sql.md)