Merge pull request #34869 from MicrosoftDocs/FromPublicRepo

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

Author: Albertyang0

azure-sql/database/intelligent-insights-troubleshoot-performance.md

@@ -166,7 +166,7 @@ Because a pagelatch is an internal control mechanism, it automatically determine
 
 One method for handling latch contention is to replace a sequential index key with a nonsequential key to evenly distribute inserts across an index range. Typically, a leading column in the index distributes the workload proportionally. Another method to consider is table partitioning. Creating a hash partitioning scheme with a computed column on a partitioned table is a common approach for mitigating excessive latch contention. In the case of pagelatch IO contention, introducing indexes helps to mitigate this performance issue.
 
-For more information, see [Diagnose and resolve latch contention on SQL Server](http://databaser.net/moniwiki/pds/PerformanceTuning/SQLServerLatchContention.pdf) (PDF download).
+For more information, see [Diagnose and resolve latch contention on SQL Server](https://learn.microsoft.com/en-us/sql/relational-databases/performance/diagnose-resolve-latch-contention-sql-server).
 
 ## Missing index