Skip to content

Commit 3e96abc

Browse files
Update intelligent-insights-troubleshoot-performance.md
1 parent b7e4aee commit 3e96abc

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -166,7 +166,7 @@ Because a pagelatch is an internal control mechanism, it automatically determine
166166

167167
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.
168168

169-
For more information, see [Diagnose and resolve latch contention on SQL Server](http://databaser.net/moniwiki/pds/PerformanceTuning/SQLServerLatchContention.pdf) (PDF download).
169+
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).
170170

171171
## Missing index
172172

0 commit comments

Comments
 (0)