[SCOPED] Fix build suggestions

rwestMSFT · rwestMSFT · commit 4e9745e04993 · 2024-01-25T16:47:52.000-07:00
diff --git a/azure-sql/database/dns-alias-powershell-create.md b/azure-sql/database/dns-alias-powershell-create.md
@@ -14,7 +14,7 @@ ms.custom:
   - devx-track-azurecli
   - devx-track-azurepowershell
 keywords: dns sql database
-ms.devlang: PowerShell
+ms.devlang: powershell
 ---
 # PowerShell for DNS Alias to Azure SQL Database
 [!INCLUDE[appliesto-sqldb-asa](../includes/appliesto-sqldb-asa.md)]
diff --git a/azure-sql/database/powershell-script-content-guide.md b/azure-sql/database/powershell-script-content-guide.md
@@ -10,7 +10,7 @@ ms.service: sql-db-mi
 ms.subservice: development
 ms.topic: sample
 ms.custom: sqldbrb=2, devx-track-azurepowershell
-ms.devlang: PowerShell
+ms.devlang: powershell
 ---
 
 # Azure PowerShell samples for Azure SQL Database and Azure SQL Managed Instance
diff --git a/azure-sql/database/scripts/add-database-to-failover-group-powershell.md b/azure-sql/database/scripts/add-database-to-failover-group-powershell.md
@@ -11,7 +11,7 @@ ms.topic: sample
 ms.custom:
   - sqldbrb=1
   - devx-track-azurepowershell
-ms.devlang: PowerShell
+ms.devlang: powershell
 ---
 
 # Use PowerShell to add a database to a failover group
diff --git a/azure-sql/database/scripts/add-elastic-pool-to-failover-group-powershell.md b/azure-sql/database/scripts/add-elastic-pool-to-failover-group-powershell.md
@@ -11,7 +11,7 @@ ms.topic: sample
 ms.custom:
   - sqldbrb=1
   - devx-track-azurepowershell
-ms.devlang: PowerShell
+ms.devlang: powershell
 ---
 # Use PowerShell to add an elastic pool to a failover group
 [!INCLUDE[appliesto-sqldb](../../includes/appliesto-sqldb.md)]
diff --git a/azure-sql/database/scripts/copy-database-to-new-server-powershell.md b/azure-sql/database/scripts/copy-database-to-new-server-powershell.md
@@ -11,7 +11,7 @@ ms.topic: sample
 ms.custom:
   - sqldbrb=1
   - devx-track-azurepowershell
-ms.devlang: PowerShell
+ms.devlang: powershell
 ---
 # Use PowerShell to copy a database to a new server
 [!INCLUDE[appliesto-sqldb](../../includes/appliesto-sqldb.md)]
diff --git a/azure-sql/database/scripts/create-and-configure-database-powershell.md b/azure-sql/database/scripts/create-and-configure-database-powershell.md
@@ -11,7 +11,7 @@ ms.topic: sample
 ms.custom:
   - sqldbrb=1
   - devx-track-azurepowershell
-ms.devlang: PowerShell
+ms.devlang: powershell
 ---
 # Use PowerShell to create a single database and configure a server-level firewall rule
 
diff --git a/azure-sql/database/scripts/import-from-bacpac-powershell.md b/azure-sql/database/scripts/import-from-bacpac-powershell.md
@@ -12,7 +12,7 @@ ms.custom:
   - "load & move data"
   - "sqldbrb=1"
   - "devx-track-azurepowershell"
-ms.devlang: PowerShell
+ms.devlang: powershell
 ---
 # Use PowerShell to import a BACPAC file into a database in SQL Database
 [!INCLUDE[appliesto-sqldb](../../includes/appliesto-sqldb.md)]
diff --git a/azure-sql/database/scripts/monitor-and-scale-database-powershell.md b/azure-sql/database/scripts/monitor-and-scale-database-powershell.md
@@ -11,7 +11,7 @@ ms.topic: sample
 ms.custom:
   - sqldbrb=1
   - devx-track-azurepowershell
-ms.devlang: PowerShell
+ms.devlang: powershell
 ---
 
 # Use PowerShell to monitor and scale a single database in Azure SQL Database
diff --git a/azure-sql/database/scripts/monitor-and-scale-pool-powershell.md b/azure-sql/database/scripts/monitor-and-scale-pool-powershell.md
@@ -11,7 +11,7 @@ ms.topic: sample
 ms.custom:
   - sqldbrb=1
   - devx-track-azurepowershell
-ms.devlang: PowerShell
+ms.devlang: powershell
 ---
 # Use PowerShell to monitor and scale an elastic pool in Azure SQL Database
 [!INCLUDE[appliesto-sqldb](../../includes/appliesto-sqldb.md)]
diff --git a/azure-sql/database/scripts/move-database-between-elastic-pools-powershell.md b/azure-sql/database/scripts/move-database-between-elastic-pools-powershell.md
@@ -11,7 +11,7 @@ ms.topic: sample
 ms.custom:
   - sqldbrb=1
   - devx-track-azurepowershell
-ms.devlang: PowerShell
+ms.devlang: powershell
 ---
 
 # Use PowerShell to create elastic pools and move a database between them
diff --git a/azure-sql/database/scripts/restore-database-powershell.md b/azure-sql/database/scripts/restore-database-powershell.md
@@ -9,7 +9,7 @@ ms.service: sql-database
 ms.subservice: backup-restore
 ms.topic: sample
 ms.custom: devx-track-azurepowershell
-ms.devlang: PowerShell
+ms.devlang: powershell
 ---
 
 # Use PowerShell to restore a database to an earlier point in time
diff --git a/azure-sql/database/scripts/setup-geodr-and-failover-database-powershell.md b/azure-sql/database/scripts/setup-geodr-and-failover-database-powershell.md
@@ -11,7 +11,7 @@ ms.topic: sample
 ms.custom:
   - sqldbrb=1
   - devx-track-azurepowershell
-ms.devlang: PowerShell
+ms.devlang: powershell
 ---
 
 # Use PowerShell to configure active geo-replication for a database in Azure SQL Database
diff --git a/azure-sql/database/scripts/setup-geodr-and-failover-elastic-pool-powershell.md b/azure-sql/database/scripts/setup-geodr-and-failover-elastic-pool-powershell.md
@@ -11,7 +11,7 @@ ms.topic: sample
 ms.custom:
   - sqldbrb=1
   - devx-track-azurepowershell
-ms.devlang: PowerShell
+ms.devlang: powershell
 ---
 # Use PowerShell to configure active geo-replication for a pooled database in Azure SQL Database
 
diff --git a/azure-sql/database/scripts/sql-data-sync-sync-data-between-azure-onprem.md b/azure-sql/database/scripts/sql-data-sync-sync-data-between-azure-onprem.md
@@ -11,7 +11,7 @@ ms.topic: sample
 ms.custom:
   - sqldbrb=1
   - devx-track-azurepowershell
-ms.devlang: PowerShell
+ms.devlang: powershell
 ---
 
 # Use PowerShell to sync data between SQL Database and SQL Server
diff --git a/azure-sql/database/scripts/sql-data-sync-sync-data-between-sql-databases.md b/azure-sql/database/scripts/sql-data-sync-sync-data-between-sql-databases.md
@@ -11,7 +11,7 @@ ms.topic: sample
 ms.custom:
   - sqldbrb=1
   - devx-track-azurepowershell
-ms.devlang: PowerShell
+ms.devlang: powershell
 ---
 
 # Use PowerShell to sync data between multiple databases in Azure SQL Database
diff --git a/azure-sql/database/scripts/update-sync-schema-in-sync-group.md b/azure-sql/database/scripts/update-sync-schema-in-sync-group.md
@@ -9,7 +9,7 @@ ms.service: sql-database
 ms.subservice: sql-data-sync
 ms.topic: sample
 ms.custom: sqldbrb=1, devx-track-azurepowershell
-ms.devlang: PowerShell
+ms.devlang: powershell
 ---
 # Use PowerShell to update the sync schema in an existing sync group
 [!INCLUDE[appliesto-sqldb](../../includes/appliesto-sqldb.md)]
diff --git a/azure-sql/database/scripts/vnet-service-endpoint-rule-powershell-create.md b/azure-sql/database/scripts/vnet-service-endpoint-rule-powershell-create.md
@@ -11,7 +11,7 @@ ms.topic: conceptual
 ms.custom:
   - sqldbrb=1
   - devx-track-azurepowershell
-ms.devlang: PowerShell
+ms.devlang: powershell
 tags: azure-synapse
 ---
 # PowerShell: Create a Virtual Service endpoint and VNet rule for Azure SQL Database
diff --git a/azure-sql/managed-instance/scripts/add-to-failover-group-powershell.md b/azure-sql/managed-instance/scripts/add-to-failover-group-powershell.md
@@ -12,7 +12,7 @@ ms.topic: sample
 ms.custom:
   - sqldbrb=1
   - devx-track-azurepowershell
-ms.devlang: PowerShell
+ms.devlang: powershell
 ---
 # Use PowerShell to add a managed instance to a failover group 
 
diff --git a/azure-sql/managed-instance/scripts/create-configure-managed-instance-powershell.md b/azure-sql/managed-instance/scripts/create-configure-managed-instance-powershell.md
@@ -10,7 +10,7 @@ ms.service: sql-managed-instance
 ms.subservice: deployment-configuration
 ms.topic: sample
 ms.custom: devx-track-azurepowershell
-ms.devlang: PowerShell
+ms.devlang: powershell
 ---
 # Use PowerShell to create a managed instance
 
diff --git a/azure-sql/managed-instance/scripts/restore-geo-backup.md b/azure-sql/managed-instance/scripts/restore-geo-backup.md
@@ -9,7 +9,7 @@ ms.service: sql-managed-instance
 ms.subservice: backup-restore
 ms.topic: sample
 ms.custom: devx-track-azurepowershell
-ms.devlang: PowerShell
+ms.devlang: powershell
 ---
 # Use PowerShell to restore an Azure SQL Managed Instance database to another geo-region
 
diff --git a/docs/database-engine/install-windows/install-sql-server-with-powershell-desired-state-configuration.md b/docs/database-engine/install-windows/install-sql-server-with-powershell-desired-state-configuration.md
@@ -8,7 +8,7 @@ ms.service: sql
 ms.subservice: install
 ms.topic: conceptual
 ms.custom: intro-installation
-ms.devlang: PowerShell
+ms.devlang: powershell
 monikerRange: ">=sql-server-2016"
 ---
 
diff --git a/docs/linux/sql-server-linux-availability-group-cluster-pacemaker.md b/docs/linux/sql-server-linux-availability-group-cluster-pacemaker.md
@@ -263,7 +263,7 @@ Manually fail over the availability group with `pcs`. Don't initiate failover wi
 
 The clustering layer is based on SUSE [High Availability Extension (HAE)](https://www.suse.com/products/highavailability) built on top of [Pacemaker](https://clusterlabs.org/).
 
-For more information on cluster configuration, resource agent options, management, best practices, and recommendations, see [SUSE Linux Enterprise High Availability Extension](https://documentation.suse.com/sle-ha/12-SP4/).
+For more information on cluster configuration, resource agent options, management, best practices, and recommendations, see [SUSE Linux Enterprise High Availability Extension](https://documentation.suse.com/sle-ha/12-SP5/).
 
 ### Roadmap
 
@@ -280,7 +280,7 @@ The procedure for creating an availability group for high availability differs b
    > [!IMPORTANT]  
    > Production environments require a fencing agent for high availability. The examples in this article don't use fencing agents. They are for testing and validation only.
    >
-   > A Linux cluster uses fencing to return the cluster to a known state. The way to configure fencing depends on the distribution and the environment. Currently, fencing isn't available in some cloud environments. For more information, see [SUSE Linux Enterprise High Availability Extension](https://documentation.suse.com/sle-ha/12-SP4/html/SLE-HA-all/cha-ha-fencing.html).
+   > A Linux cluster uses fencing to return the cluster to a known state. The way to configure fencing depends on the distribution and the environment. Currently, fencing isn't available in some cloud environments. For more information, see [SUSE Linux Enterprise High Availability Extension](https://documentation.suse.com/sle-ha/12-SP5/html/SLE-HA-all/cha-ha-fencing.html).
 
 1. [Add the availability group as a resource in the cluster](#configure-an-availability-group)
 
@@ -315,7 +315,7 @@ The first step is to configure the operating system on the cluster nodes. For th
    sudo crm_report -X "-p 3479" [...]
    ```
 
-   For more information, see the [SLES Administration Guide - Miscellaneous section](https://documentation.suse.com/sles/12-SP4/html/SLES-all/part-trouble.html).
+   For more information, see the [SLES Administration Guide - Miscellaneous section](https://documentation.suse.com/sles/12-SP5/html/SLES-all/part-trouble.html).
 
 ### Create a SQL Server login for Pacemaker
 
@@ -329,7 +329,7 @@ On Linux servers, configure the availability group and then configure the cluste
 
 1. Install the High Availability extension
 
-   For reference, see [Installing SUSE Linux Enterprise Server and High Availability Extension](https://documentation.suse.com/sle-ha/12-SP4/html/SLE-HA-install-quick/art-ha-install-quick.html).
+   For reference, see [Installing SUSE Linux Enterprise Server and High Availability Extension](https://documentation.suse.com/sle-ha/12-SP5/html/SLE-HA-all/art-ha-install-quick.html).
 
 1. Install [!INCLUDE [ssnoversion-md](../includes/ssnoversion-md.md)] resource agent package on both nodes.
 
@@ -339,7 +339,7 @@ On Linux servers, configure the availability group and then configure the cluste
 
 ### Set up the first node
 
-   Refer to [SLES installation instructions](https://documentation.suse.com/sle-ha/12-SP4/).
+   Refer to [SLES installation instructions](https://documentation.suse.com/sle-ha/12-SP5/).
 
 1. Sign in as `root` to the physical or virtual machine you want to use as cluster node.
 1. Start the bootstrap script by executing:
@@ -384,7 +384,7 @@ If you have a cluster running with one or more nodes, add more cluster nodes wit
 If you have configured the existing cluster nodes with the `YaST` cluster module, make sure the following prerequisites are fulfilled before you run `ha-cluster-join`:
 
 - The root user on the existing nodes has SSH keys in place for passwordless login.
-- `Csync2` is configured on the existing nodes. For more information, see [Configuring Csync2 with YaST](https://documentation.suse.com/sle-ha/12-SP4/html/SLE-HA-all/cha-ha-setup.html#pro-ha-installation-setup-csync2-yast).
+- `Csync2` is configured on the existing nodes. For more information, see [Configuring Csync2 with YaST](https://documentation.suse.com/sle-ha/12-SP5/html/SLE-HA-all/cha-ha-setup.html#pro-ha-installation-setup-csync2-yast).
 
 1. Sign in as `root` to the physical or virtual machine supposed to join the cluster.
 1. Start the bootstrap script by executing:
@@ -483,7 +483,7 @@ sudo crm configure property stonith-enabled=true
 
 ### Configure the cluster resources for SQL Server
 
-Refer to the [SLES Administration Guide](https://documentation.suse.com/sle-ha/12-SP4/).
+Refer to the [SLES Administration Guide](https://documentation.suse.com/sle-ha/12-SP5/).
 
 ### Enable Pacemaker
 
@@ -579,7 +579,7 @@ Manually fail over the availability group with `crm`. Don't initiate failover wi
 
 For more information, see:
 
-- [SUSE Linux Enterprise High Availability Extension 12 SP4](https://documentation.suse.com/sle-ha/12-SP4/)
+- [SUSE Linux Enterprise High Availability Extension 12 SP4](https://documentation.suse.com/sle-ha/12-SP5/)
 - [Pacemaker Quick Reference](https://github.com/ClusterLabs/pacemaker/blob/master/doc/sphinx/Pacemaker_Administration/pcs-crmsh.rst)
 
 ## Related content
diff --git a/docs/linux/sql-server-linux-availability-group-configure-ha.md b/docs/linux/sql-server-linux-availability-group-configure-ha.md
@@ -47,7 +47,7 @@ The steps to create an AG on Linux servers for high availability are different f
    >
    > A Pacemaker cluster uses fencing to return the cluster to a known state. The way to configure fencing depends on the distribution and the environment. Currently, fencing isn't available in some cloud environments. For more information, see [Support Policies for RHEL High Availability Clusters - Virtualization Platforms](https://access.redhat.com/articles/2912891).
    >  
-   > For SLES, see [SUSE Linux Enterprise High Availability Extension](https://documentation.suse.com/sle-ha/12-SP4/#redirectmsg).
+   > For SLES, see [SUSE Linux Enterprise High Availability Extension](https://documentation.suse.com/sle-ha/12-SP5/#redirectmsg).
 
 1. Add the AG as a resource in the cluster.
 
diff --git a/docs/relational-databases/performance/intelligent-query-processing-cardinality-estimation-feedback.md b/docs/relational-databases/performance/intelligent-query-processing-cardinality-estimation-feedback.md
@@ -160,7 +160,7 @@ Starting with [!INCLUDE[sssql22-md](../../includes/sssql22-md.md)] Cumulative Up
 
 This issue does not affect all workloads, and depends on the number of different plans that have been generated as well as the number of plans that were eligible for the CE feedback feature to engage. During the period of time that CE feedback is analyzing plan operators where significant model misestimations occurred, there is a scenario in which during this analysis phase, a plan that was being referenced can become dereferenced in memory without allowing the plan to subsequently be removed from memory by way of the normal Least Recently Used (LRU) algorithm. The LRU mechanism one way that SQL Server enforces plan eviction policies. SQL Server will also remove plans from memory if the system is under memory pressure. When SQL Server attempts to remove the plans that have been dereferenced improperly, it is unable to remove those plans from the plan cache, which causes the cache to continue to grow. The growing cache might start to cause additional compilations that will ultimately use more CPU and memory. For more information, see [Plan Cache Internals](/previous-versions/tn-archive/cc293624(v=technet.10)).
 
-**Symptom**: The number of plan cache **entries in use** and are marked as **dirty** from either SQL Plans or Object Plans increases over time to 50,000 or more. If you observe plan cache entries that start to approach this level along with unexpected increases in CPU utilization, your system may be encountering this issue. A related fix was provided in [!INCLUDE[sssql22-md](../../includes/sssql22-md.md)] Cumulative Update 9. See [KB5030731](https://learn.microsoft.com/troubleshoot/sql/releases/sqlserver-2022/cumulativeupdate9#2499342). The fix attempted to address an issue in which plan cache entries are evicted when the Cardinality Estimation (CE) feedback tries to get the associated profile, which causes a memory corruption. Additional fixes for this issue will be available in an upcomming Cumulative Update.
+**Symptom**: The number of plan cache **entries in use** and are marked as **dirty** from either SQL Plans or Object Plans increases over time to 50,000 or more. If you observe plan cache entries that start to approach this level along with unexpected increases in CPU utilization, your system may be encountering this issue. A related fix was provided in [!INCLUDE[sssql22-md](../../includes/sssql22-md.md)] Cumulative Update 9. See [KB5030731](/troubleshoot/sql/releases/sqlserver-2022/cumulativeupdate9#2499342). The fix attempted to address an issue in which plan cache entries are evicted when the Cardinality Estimation (CE) feedback tries to get the associated profile, which causes a memory corruption. Additional fixes for this issue will be available in an upcomming Cumulative Update.
 
 To monitor the number of plan cache entries that your system is using, the following examples can be used as a point in time view of the number of plan cache entries that exist. As an example, watching the number of plan cache entries that are marked as dirty, periodically over time is one way to monitor for this phenomenon.
 
