Merge remote-tracking branch 'upstream/main' into 7530-update-headings

Author: haywoodsloan

support/sql/analysis-services/configure-msolap-data-provider-excel.md

@@ -27,7 +27,7 @@ To create a data connection to an Analysis Services data source, Microsoft Excel
 
 For more information about MSOLAP and other client libraries for Analysis Services, review [Analysis Services client libraries](/analysis-services/client-libraries).
 
-For more information about how to use the correct version of MSOLAP, see [Connection string properties](/analysis-services/instances/connection-string-properties-analysis-services). For legacy MSOLAP versions, please refer to [How to obtain the latest versions of MSOLAP](https://support.microsoft.com/help/2735567). For latest MSOLAP version, please refer to [Analysis Services client libraries](/analysis-services/client-libraries).
+For more information about how to use the correct version of MSOLAP, see [Connection string properties](/analysis-services/instances/connection-string-properties-analysis-services). For latest MSOLAP version, please refer to [Analysis Services client libraries](/analysis-services/client-libraries).
 
 Excel uses the version of the MSOLAP provider that is installed on the client device. In the following example, Excel has configured MSOLAP.5 as the data provider in the data connection string.
 

support/sql/database-engine/backup-restore/backup-restore-operations.md

@@ -214,7 +214,7 @@ You fail to restore a CRM backup from the Enterprise edition on a Standard editi
 
 **Resolution**
 
-To solve the issue, see [2567984 "Database cannot be started in this edition of SQL Server" error when restoring a Microsoft Dynamics CRM database](https://support.microsoft.com/help/2567984).
+To solve the issue, see ["Database cannot be started in this edition of SQL Server" error when restoring a Microsoft Dynamics CRM database](/previous-versions/troubleshoot/dynamics/crm/database-cannot-be-started-in-this-edition-of-sql-error-when-restoring).
   
 ## FAQ about SQL Server backup and restore operations
 

support/sql/database-engine/database-file-operations/defragmenting-database-disk-drives.md

@@ -59,4 +59,4 @@ Open-file defragmentation raises several possible issues that closed-file defrag
 
 - [How to run ChkDsk and defrag on Cluster Shared Volumes in Windows Server 2012 R2](https://techcommunity.microsoft.com/t5/failover-clustering/how-to-run-chkdsk-and-defrag-on-cluster-shared-volumes-in/ba-p/371905)
 
-- [Recommendations and guidelines for improving SQL Server FILESTREAM performance](https://support.microsoft.com/help/2160002)
+- [Recommendations and guidelines for improving SQL Server FILESTREAM performance](/sql/relational-databases/blob/filestream-sql-server)

support/sql/database-engine/failover-clusters/windows-failover-cluster-resource-depend.md

@@ -18,8 +18,7 @@ _Original KB number:_   835185
 When you install SQL Server on a cluster as a SQL Server failover cluster instance, a specific set of SQL Server resources that have dependencies on other resources in the cluster group are created.
 
 > [!IMPORTANT]
-> Don't change the default dependency tree except for the changes that are listed in this article or the changes that are listed in the following article in the Microsoft Knowledge Base:
-[SQL Server support for mounted folders](https://support.microsoft.com/help/819546)
+> Don't change the default dependency tree except for the changes that are listed in this article
 
 ## Example 1 - Default SQL Server failover cluster instance dependencies
 

support/sql/database-engine/general/error-556-insert-exec-failed.md

@@ -37,7 +37,7 @@ The auto-cleanup process flushes the plan out of Query Data Store. The query enc
 
 This issue is fixed in the following service pack for SQL Server:  
 
-[Service Pack 3 for SQL Server 2016](https://support.microsoft.com/help/5003279)
+[Service Pack 3 for SQL Server 2016](~/sql/releases/sqlserver-2016/servicepack3.md)
 
 **About service packs for SQL Server:**  
 

support/sql/database-engine/install/windows/support-policy-hardware-virtualization-product.md

@@ -50,11 +50,7 @@ The following restrictions and limitations may affect the support policy of the
 - Guest Failover Clustering is supported for SQL Server in a virtual machine for the supported hardware virtualization environments listed in this article provided all the following requirements are met:
 
   - The Operating System running in the virtual machine (the "Guest Operating System") is a Windows Server version currently in support lifecycle.
-  - The virtualization environment meets the requirements of Windows Server or Windows Server Failover Clustering, as documented in the following articles in the Microsoft Knowledge Base:
-  
-    - [The Microsoft Support Policy for Windows Server 2008 or Windows Server 2008 R2 Failover Clusters](https://support.microsoft.com/help/943984)
-
-    - [Microsoft support policy for Windows server failover clusters](../../../../windows-server/high-availability/microsoft-support-policy-failover-clusters.md)
+  - The virtualization environment meets the requirements of Windows Server or Windows Server Failover Clustering, as documented in [Microsoft support policy for Windows server failover clusters](~/windows-server/high-availability/microsoft-support-policy-failover-clusters.md)
 
 - The SQL Server product must be a supported version under its current Microsoft Support Lifecycle policy. For more information about Microsoft Support Lifecycle policies, see [Search Product and Services Lifecycle Information](/lifecycle/products/).
 

support/sql/database-engine/performance/buffer-pool-scan-runs-slowly-large-memory-machines.md

@@ -33,13 +33,13 @@ Here are some operations that may trigger a buffer pool scan to occur:
 
 ### Error log shows that a scan took a long time
 
-Starting with [SQL Server 2016 SP3](https://support.microsoft.com/help/5003279), [SQL Server 2017 CU23](https://prod.support.services.microsoft.com/topic/kb5000685-cumulative-update-23-for-sql-server-2017-22b653c7-8487-4564-9db2-b5c1bd465145?preview=true#bkmk_13741858) and [SQL Server 2019 CU9](https://support.microsoft.com/topic/kb5000642-cumulative-update-9-for-sql-server-2019-97ad5c3e-e002-4b6d-b566-698bf70ca44a#bkmk_13744390), an error message was added to the SQL Server [Error log](/sql/tools/configuration-manager/viewing-the-sql-server-error-log) to indicate that a buffer pool scan took a long time (10 seconds or longer):
+Starting with [SQL Server 2016 SP3](~/sql/releases/sqlserver-2016/servicepack3.md), [SQL Server 2017 CU23](~/sql/releases/sqlserver-2017/cumulativeupdate23.md#13741858) and [SQL Server 2019 CU9](~/sql/releases/sqlserver-2019/cumulativeupdate9.md#13744390), an error message was added to the SQL Server [Error log](/sql/tools/configuration-manager/viewing-the-sql-server-error-log) to indicate that a buffer pool scan took a long time (10 seconds or longer):
 
 > Buffer Pool scan took 14 seconds: database ID 7, command 'BACKUP DATABASE', operation 'FlushCache', scanned buffers 115, total iterated buffers 204640239, wait time 0 ms. See 'https://go.microsoft.com/fwlink/?linkid=2132602' for more information.
 
 ### Extended Event to diagnose a long scan
 
-Also, starting with the same builds [SQL Server 2016 SP3](https://support.microsoft.com/help/5003279), [SQL Server 2017 CU23](https://prod.support.services.microsoft.com/topic/kb5000685-cumulative-update-23-for-sql-server-2017-22b653c7-8487-4564-9db2-b5c1bd465145?preview=true#bkmk_13741858) and [SQL Server 2019 CU9](https://support.microsoft.com/topic/kb5000642-cumulative-update-9-for-sql-server-2019-97ad5c3e-e002-4b6d-b566-698bf70ca44a#bkmk_13744390)  the **buffer_pool_scan_complete** Extended event was introduced to help you identify long buffer pool scans.
+Also, starting with the same builds [SQL Server 2016 SP3](~/sql/releases/sqlserver-2016/servicepack3.md), [SQL Server 2017 CU23](~/sql/releases/sqlserver-2017/cumulativeupdate23.md#13741858) and [SQL Server 2019 CU9](~/sql/releases/sqlserver-2019/cumulativeupdate9.md#13744390)  the **buffer_pool_scan_complete** Extended event was introduced to help you identify long buffer pool scans.
 
 If a scan takes more than 1 second, the XEvent will be recorded as follows when the event is enabled.
 

support/sql/database-engine/performance/recommended-updates-configuration-workloads.md

@@ -70,7 +70,7 @@ Review the content in the **Knowledge Base article or Books Online Resource** co
 | [Compute capacity limits by edition](/sql/sql-server/compute-capacity-limits-by-edition-of-sql-server) The license core limitation for SQL Server 2012|Enterprise Edition that has Server and Client Access License (CAL) licensing is limited to 20 cores per SQL Server instance.<br/><br/>There are no limits under the Core-based Server Licensing model.<br/><br/>Consider upgrading your edition of SQL Server to the appropriate SKU to use all hardware resources.|
 | [Slow performance on Windows Server when using the Balanced power plan](../../../windows-server/performance/slow-performance-when-using-power-plan.md) |Review the article, and work together with your Windows administrator to implement one of the solutions that are listed in the Resolution section of the article.|
 | [optimize for ad hoc workloads Server Configuration Option](/sql/database-engine/configure-windows/optimize-for-ad-hoc-workloads-server-configuration-option) </br></br>[FORCED PARAMETERIZATION](/sql/relational-databases/query-processing-architecture-guide)| Entries in the plan cache are evicted because of growth in other caches or memory clerks. You might also encounter plan cache eviction when the cache reaches its maximum number of entries. In addition to trace flag 8032 discussed above, consider the [optimize for ad hoc workloads](/sql/database-engine/configure-windows/optimize-for-ad-hoc-workloads-server-configuration-option) server option and also the [FORCED PARAMETERIZATION](/sql/relational-databases/query-processing-architecture-guide) database option. |
-| [How to reduce paging of buffer pool memory in SQL Server](https://support.microsoft.com/help/918483)<br/><br/> [Memory configuration and sizing considerations in SQL Server 2012 and later versions](https://support.microsoft.com/help/2663912/) | Assign the [Lock Pages in Memory Option (Windows)](/sql/database-engine/configure-windows/enable-the-lock-pages-in-memory-option-windows) user right to the SQL service Startup account. <br/><br/>Set maximum server memory to approximately 90 percent of total physical memory. Make sure that the [Server memory configuration options](/sql/database-engine/configure-windows/server-memory-server-configuration-options) setting accounts for memory from only the nodes that are configured to use affinity mask settings. |
+| [How to reduce paging of buffer pool memory in SQL Server](https://support.microsoft.com/help/918483)<br/><br/> [Memory configuration and sizing considerations in SQL Server 2012 and later versions](/sql/relational-databases/memory-management-architecture-guide) | Assign the [Lock Pages in Memory Option (Windows)](/sql/database-engine/configure-windows/enable-the-lock-pages-in-memory-option-windows) user right to the SQL service Startup account. <br/><br/>Set maximum server memory to approximately 90 percent of total physical memory. Make sure that the [Server memory configuration options](/sql/database-engine/configure-windows/server-memory-server-configuration-options) setting accounts for memory from only the nodes that are configured to use affinity mask settings. |
 | [SQL Server and Large Pages Explained...](/archive/blogs/psssql/sql-server-and-large-pages-explained) | Consider enabling [Trace Flag 834](/sql/t-sql/database-console-commands/dbcc-traceon-trace-flags-transact-sql#tf834) if you have a server that has much memory, particularly for an analytical or data warehousing workload. Keep in mind that [Interoperability of Columnstore indexes with large page memory model in SQL Server](https://support.microsoft.com/kb/3210239). |
 | [Query Performance issues associated with a large sized security cache](/archive/blogs/psssql/query-performance-issues-associated-with-a-large-sized-security-cache) <br/><br/>[Queries take a longer time to finish running when the size of the TokenAndPermUserStore cache grows in SQL Server](https://support.microsoft.com/topic/queries-take-a-longer-time-to-finish-running-when-the-size-of-the-tokenandpermuserstore-cache-grows-in-sql-server-2005-ad1622e7-3bb5-7902-19a0-5d0e6271033d) <br/><br/>[DBCC TRACEON - Trace Flags (Transact-SQL)](/sql/t-sql/database-console-commands/dbcc-traceon-trace-flags-transact-sql)| If the security cache grows to a large size and you encounter performance problems and spinlock contention, consider enabling trace flag [T4610](/sql/t-sql/database-console-commands/dbcc-traceon-trace-flags-transact-sql#tf4610) and [T4618](/sql/t-sql/database-console-commands/dbcc-traceon-trace-flags-transact-sql#tf4618) to reduce the maximum size of TokenAndPermuserStore. |
 | [ALTER WORKLOAD GROUP](/sql/t-sql/statements/alter-workload-group-transact-sql) [KB3107401 - New query memory grant options are available (min_grant_percent and max_grant_percent) in SQL Server 2012](https://support.microsoft.com/help/3107401)| If you have many queries that are exhausting large memory grants, reduce `request_max_memory_grant_percent` for the default workload group in the resource governor configuration from the default 25 percent to a lower value. New query memory grant options are available (`min_grant_percent` and `max_grant_percent`) in SQL Server. |

support/sql/database-engine/replication/ascii-function-returns-different-results-publisher-subscriber.md

@@ -68,6 +68,6 @@ In this scenario, when you use the `ASCII` function to convert the column in the
 
 - To work around this issue for merge replication, follow these steps:
 
-    1. Apply [SQL Server 2019 Cumulative Update 15 (CU15)](https://support.microsoft.com/help/5008996) or a later version on the Distributor server.
+    1. Apply [SQL Server 2019 Cumulative Update 15 (CU15)](~/sql/releases/sqlserver-2019/cumulativeupdate15.md) or a later version on the Distributor server.
 
     1. Follow all the steps that are applied to the transactional replication issue.

support/sql/database-engine/replication/understand-merge-replication-article-process.md

@@ -78,7 +78,7 @@ The Merge Agent processes generations in batches, also referred to as generation
 
 In a situation where multiple generation batches are exchanged, the Merge Agent may split related parent and child changes across two separate generation batches. If that is the case, the Merge Agent may deliver a child change in a generation batch ahead of the generation batch that contains the associated parent change. In hierarchical merge topologies that use re-publishers, there is one rare situation in which the splitting of parent and child changes across generation batches can lead to non-convergence. For more information about non-convergence, see the following article:
 
-[Non-convergence when SQL Server processes child and parent generations in separate generation batches](https://support.microsoft.com/help/308266).  
+[Non-convergence when SQL Server processes child and parent generations in separate generation batches](~/sql/database-engine/replication/non-convergence-when-processes-child-generations.md).  
 
 You can increase the `-UploadGenerationsPerBatch` and the `-DownloadGenerationsPerBatch` parameters discussed previously to avoid splitting parent and child changes across generation batches.