Merge branch 'master' into 20210915-ws2022-for-SQL

Author: WilliamDAssafMSFT

docs/ado/guide/data/what-is-a-cursor.md

@@ -4,11 +4,12 @@ title: "What is a Cursor? | Microsoft Docs"
 ms.prod: sql
 ms.prod_service: connectivity
 ms.technology: ado
-ms.custom: ""
+ms.custom:
+  - intro-overview
 ms.date: "01/19/2017"
 ms.reviewer: ""
 ms.topic: conceptual
-helpviewer_keywords: 
+helpviewer_keywords:
   - "cursors [ADO], about cursors"
 ms.assetid: 596eb4b6-c22f-4cde-b23f-172dd66c3161
 author: rothja

docs/ado/guide/data/what-is-a-lock.md

@@ -4,11 +4,12 @@ title: "What is a Lock? | Microsoft Docs"
 ms.prod: sql
 ms.prod_service: connectivity
 ms.technology: ado
-ms.custom: ""
+ms.custom:
+  - intro-overview
 ms.date: "01/19/2017"
 ms.reviewer: ""
 ms.topic: conceptual
-helpviewer_keywords: 
+helpviewer_keywords:
   - "cursors [ADO], locking"
   - "locks [ADO], about locking"
 ms.assetid: f8989555-28c6-4c17-9bf8-7f44a8a5c407

docs/analytics-platform-system/apply-analytics-platform-system-hotfixes.md

@@ -48,7 +48,7 @@ Unlike the Microsoft updates, the hotfixes for the Analytics Platform System sof
 
     2.  Use the **Run as administrator** option to open a Command Prompt.  
 
-    3.  Run the following command, replacing *<HotfixPackageName>* with the name of the hotfix executable package, and replacing the other placeholder items *<  >* with the appropriate information.  
+    3.  Run the following command, replacing *\<HotfixPackageName\>* with the name of the hotfix executable package, and replacing the other placeholder items *<  >* with the appropriate information.  
 
         ```  
         <HotfixPackageName> /DomainAdminPassword="<password>"  

docs/analytics-platform-system/create-ssis-script-task-using-pdw-destination-adapter.md

@@ -23,7 +23,7 @@ This SSIS package script code is a code example for using the SSIS PDW destinati
 
 3.  Edit the script to use the code provided below. Customized the script to your environment by making the following changes:  
 
-    -   You must retain the namespace of the script created by the script task. Note the name of the namespace `namespace ST_<GUID>` and edit the script below, changing *ST_<GUID>* to the original *GUID* of the script task.  
+    -   You must retain the namespace of the script created by the script task. Note the name of the namespace `namespace ST_<GUID>` and edit the script below, changing *ST_\<GUID\>* to the original *GUID* of the script task.  
 
     -   Replace four occurrences of the placeholder value *XXXXXXXX* with the values appropriate to your environment and intended action.  
 

docs/analytics-platform-system/download-and-apply-microsoft-updates.md

@@ -120,7 +120,7 @@ Before performing these steps, you need to:
 
 5.  In the **Status** drop-down menu, select **Any** and click **Refresh**.  
 
-6.  Expand **Update Services**, *<appliance name>*-VMM, **Updates**, **All Updates**, where *<appliance name>* is your appliance name.  
+6.  Expand **Update Services**, *\<appliance name\>*-VMM, **Updates**, **All Updates**, where *\<appliance name\>* is your appliance name.  
 
 7.  In the **All Updates** window set **Approval** to **Any Except Declined**.  
 
@@ -144,7 +144,7 @@ Follow these instructions to run the Analytics Platform System Update program.
   
 1.  Make sure you are logged into the HST01 node as the Fabric Domain Administrator.  
 
-2.  Open a Command Prompt window and enter the following commands. Replace *<parameter>* with the designated information.  
+2.  Open a Command Prompt window and enter the following commands. Replace *\<parameter\>* with the designated information.  
 
 **To Run the Microsoft Update:**  
 

docs/analytics-platform-system/dwloader.md

@@ -142,7 +142,7 @@ Examples:
 **-S** *target_appliance*  
 Specifies the SQL Server PDW appliance that will receive the loaded data.  
 
-*For Infiniband connections*, *target_appliance* is specified as <appliance-name>-SQLCTL01. To configure this named connection, see [Configure InfiniBand Network Adapters](configure-infiniband-network-adapters.md).  
+*For Infiniband connections*, *target_appliance* is specified as \<appliance-name\>-SQLCTL01. To configure this named connection, see [Configure InfiniBand Network Adapters](configure-infiniband-network-adapters.md).  
 
 For Ethernet connections, *target_appliance* is the IP address for the Control node cluster.  
 
@@ -690,7 +690,7 @@ Description of the command-line parameters:
 
 -   *-r \r\n* specifies each row in DimAccount.txt ends with a carriage return and a line feed character.  
 
--   *-U <login_name> -P <password>* specifies the login and password for the login that has permissions to perform the load.  
+-   *-U <login_name> -P \<password\>* specifies the login and password for the login that has permissions to perform the load.  
 
 
 <!-- MISSING LINK

docs/analytics-platform-system/install-the-scom-management-packs.md

@@ -1,14 +1,16 @@
 ---
 title: Install SCOM management packs
-description: Follow these steps to download and install the System Center Operations Manager (SCOM) Management Packs for SQL Server PDW. The Management Packs are required to monitor SQL Server PDW from SCOM. 
-author: charlesfeddersen 
+description: Follow these steps to download and install the System Center Operations Manager (SCOM) Management Packs for SQL Server PDW. The Management Packs are required to monitor SQL Server PDW from SCOM.
+author: charlesfeddersen
 ms.prod: sql
 ms.technology: data-warehouse
 ms.topic: conceptual
 ms.date: 04/17/2018
 ms.author: charlesf
 ms.reviewer: martinle
-ms.custom: seo-dt-2019
+ms.custom:
+  - seo-dt-2019
+  - intro-installation
 ---
 
 # Install SQL Server Operations Manager (SCOM) management packs for Analytics Platform System
@@ -74,4 +76,4 @@ For older versions of PDW without APS, download the[System Center Monitoring Pac
 Now that you have the Management Packs installed, continue to the next step: [Import the SCOM Management Pack for PDW (Analytics Platform System)](import-the-scom-management-pack-for-pdw.md).  
 
 <!-- MISSING LINKS ## See Also  
-[Common Metadata Query Examples &#40;SQL Server PDW&#41;](../sqlpdw/common-metadata-query-examples-sql-server-pdw.md)  -->
+[Common Metadata Query Examples &#40;SQL Server PDW&#41;](../sqlpdw/common-metadata-query-examples-sql-server-pdw.md)  -->

docs/analytics-platform-system/load-with-ssis.md

@@ -213,7 +213,7 @@ Specify the destination for the data flow.
 
 5.  Fill in the information for the server, user, password, and destination database with information specific to your appliance. (Examples are shown below). Then click **OK**.  
 
-    For InfiniBand connections, **Server name**: Enter <appliance-name>-SQLCTL01,17001.  
+    For InfiniBand connections, **Server name**: Enter \<appliance-name\>-SQLCTL01,17001.  
 
     For Ethernet connections, **Server name**: Enter the IP address of the Control node cluster, comma, port 17001. For example, 10.192.63.134,17001.  
 

docs/analytics-platform-system/pdw-permissions.md

@@ -92,7 +92,7 @@ An *implicit permission* is a **GRANT** or **DENY** permission that a principal
 
 -   A principal can inherit a permission on a subordinate object (such as a table) if the principal has a permission on one of the objects parent scopes (such as the  schema of the table or the permission on the entire database).
 
--   A principal can inherit a permission by having a permission that includes a subordinate permission. For example the **ALTER ANY USER** permission includes the both the **CREATE USER** and the **ALTER ON USER::**_<name>_ permissions.
+-   A principal can inherit a permission by having a permission that includes a subordinate permission. For example the **ALTER ANY USER** permission includes the both the **CREATE USER** and the **ALTER ON USER::**_\<name\>_ permissions.
 
 ### Determining Permissions When Performing Actions
 The process of determining which permission to assign to a principal is complex. The complexity occurs when determining implicit permissions because principals can be members of multiple roles and permissions can be passed through multiple levels in the role hierarchy.

docs/analytics-platform-system/transparent-data-encryption.md

@@ -239,7 +239,7 @@ Example of the action to replace a virtual machine.
 
 `setup.exe /Action=/proxy/https/github.com/MicrosoftDocs/sql-docs/commit/ReplaceVM ... DMKPassword='**********'`  
 
-During upgrade, if a user DB is encrypted and the DMK password is not provided, the upgrade action will fail. During replace, if the correct password is not provided when a DMK exists, the operation will skip the DMK recovery step. All the other steps will be completed at the end of the replace VM action, however the action will report failure at the end to indicate that additional steps are required. In the setup logs (located in **\ProgramData\Microsoft\Microsoft SQL Server Parallel Data Warehouse\100\Logs\Setup\\<time-stamp>\Detail-Setup**), the following warning will be shown near the end.  
+During upgrade, if a user DB is encrypted and the DMK password is not provided, the upgrade action will fail. During replace, if the correct password is not provided when a DMK exists, the operation will skip the DMK recovery step. All the other steps will be completed at the end of the replace VM action, however the action will report failure at the end to indicate that additional steps are required. In the setup logs (located in **\ProgramData\Microsoft\Microsoft SQL Server Parallel Data Warehouse\100\Logs\Setup\\\\<time-stamp\>\Detail-Setup**), the following warning will be shown near the end.  
 
 `*** WARNING \*\*\* DMK is detected in master database, but could not be recovered automatically! The DMK password was either not provided or is incorrect!`