20230313 1622

Author: WilliamDAssafMSFT

azure-sql/database/analyze-prevent-deadlocks.md

@@ -773,7 +773,7 @@ There are multiple techniques available to prevent deadlocks from reoccurring, i
     - Breaking apart transactions into smaller transactions when possible.
     - Using query hints, if necessary, to optimize performance. You can apply hints without changing application code [using Query Store](/sql/relational-databases/performance/query-store-hints?view=azuresqldb-current&preserve-view=true).
 
-Find more ways to [minimize deadlocks in the Deadlocks guide](/sql/relational-databases/sql-server-deadlocks-guide#deadlock_minimizing).
+Find more ways to [minimize deadlocks in the Deadlocks guide](/sql/relational-databases/sql-server-deadlocks-guide#minimize_deadlocks).
 
 > [!NOTE]
 > In some cases, you may wish to [adjust the deadlock priority](/sql/t-sql/statements/set-deadlock-priority-transact-sql) of one or more sessions involved in a deadlock if it is important for one of the sessions to complete successfully without retrying, or when one of the queries involved in the deadlock is not critical and should be always chosen as the victim. While this does not prevent the deadlock from reoccurring, it may reduce the impact of future deadlocks.

docs/relational-databases/sql-server-deadlocks-guide.md

@@ -364,22 +364,22 @@ Implementing an error handler that traps error message 1205 allows an applicatio
 
 The application should pause briefly before resubmitting its query. This gives the other transaction involved in the deadlock a chance to complete and release its locks that formed part of the deadlock cycle. This minimizes the likelihood of the deadlock reoccurring when the resubmitted query requests its locks.  
 
-## <a id="deadlock_minimizing"></a> Minimize deadlocks
+## Minimize deadlocks
 
 Although deadlocks cannot be completely avoided, following certain coding conventions can minimize the chance of generating a deadlock. Minimizing deadlocks can increase transaction throughput and reduce system overhead because fewer transactions are:  
 
--   Rolled back, undoing all the work performed by the transaction.  
--   Resubmitted by applications because they were rolled back when deadlocked.  
+- Rolled back, undoing all the work performed by the transaction.  
+- Resubmitted by applications because they were rolled back when deadlocked.  
 
 To help minimize deadlocks:  
 
--   Access objects in the same order.  
--   Avoid user interaction in transactions.  -   Keep transactions short and in one batch.  
--   Use a lower isolation level.  
--   Use a row versioning-based isolation level.  
-    -   Set `READ_COMMITTED_SNAPSHOT` database option on to enable read-committed transactions to use row versioning.  
-    -  Use snapshot isolation.  
--   Use bound connections.  
+- Access objects in the same order.  
+- Avoid user interaction in transactions.  -   Keep transactions short and in one batch.  
+- Use a lower isolation level.  
+- Use a row versioning-based isolation level.  
+  - Set `READ_COMMITTED_SNAPSHOT` database option on to enable read-committed transactions to use row versioning.  
+  - Use snapshot isolation.  
+- Use bound connections.  
 
 ### Access objects in the same order
 

docs/relational-databases/sql-server-transaction-locking-and-row-versioning-guide.md

@@ -1640,7 +1640,7 @@ The only lock taken that references `HumanResources.Employee` is a schema stabil
 
 In [!INCLUDE [ssnoversion-md](../includes/ssnoversion-md.md)], the `LOCK_ESCALATION` option of `ALTER TABLE` can disfavor table locks, and enable HoBT locks on partitioned tables. This option is not a locking hint, but can be used to reduce lock escalation. For more information, see [ALTER TABLE (Transact-SQL)](../t-sql/statements/alter-table-transact-sql.md).
 
-### <a id="Customize"></a> Customize locking for an index
+### Customize locking for an index
 
 When optimized locking is enabled, [!INCLUDE[ssDEnoversion](../includes/ssdenoversion-md.md)] does not keep low-level locks for the duration of a transaction. There is no need to customize locking strategies for an index or to disable low-level locks.
 
@@ -1826,7 +1826,7 @@ You may have to use the KILL statement. Use this statement very carefully, howev
 Deadlocks are a complex topic related to locking, but different from blocking.
 
 - For more information on deadlocks, including monitoring, diagnosis, and samples, see the [Deadlocks guide for the SQL Server database engine](sql-server-deadlocks-guide.md).
-- For more information on deadlocks specific to Azure SQL Database, see [Analyze and prevent deadlocks in Azure SQL Database](../../azure-sql/database/analyze-prevent-deadlocks.md).
+- For more information on deadlocks specific to Azure SQL Database, see [Analyze and prevent deadlocks in Azure SQL Database](/azure/azure-sql/database/analyze-prevent-deadlocks).
 
 ## <a id="Additional_Reading"></a> See also
 
@@ -1839,4 +1839,4 @@ Deadlocks are a complex topic related to locking, but different from blocking.
 ## Next steps
 
 - [Understand and resolve SQL Server blocking problems](/troubleshoot/sql/database-engine/performance/understand-resolve-blocking)
-- [Understand and resolve Azure SQL Database blocking problems](../../azure-sql/database/understand-resolve-blocking.md)
+- [Understand and resolve Azure SQL Database blocking problems](/azure/azure-sql/database/understand-resolve-blocking)