Fix relative links

Author: rwestMSFT

docs/relational-databases/errors-events/includes/sql-server-2019-database-engine-events-and-errors-22000-22999.md

@@ -2,7 +2,7 @@
 author: MashaMSFT
 ms.author: mathoma
 ms.reviewer: randolphwest
-ms.date: 03/22/2023
+ms.date: 04/21/2023
 ms.topic: include
 ---
 | Error| Severity | Event logged | Description|
@@ -42,7 +42,7 @@ ms.topic: include
 | 22122 | 16 | No | Change Tracking autocleanup failed on side table of "%s".  If the failure persists, use sp_flush_CT_internal_table_on_demand to clean up expired records from its side table. |
 | 22123 | 16 | No | Change Tracking autocleanup is blocked on side table of "%s". If the failure persists, check if the table "%s" is blocked by any process . |
 | 22124 | 16 | No | Change Tracking manual cleanup is blocked on side table of "%s". If the failure persists, check if the table "%s" is blocked by any process . |
-| 22125 | 16 | No | Change tracking autocleanup is currently not able to maintain retention for database ID %d. Number of expired records: %d. If this warning persists, check the following resource: [https://learn.microsoft.com/sql/relational-databases/track-changes/cleanup-and-troubleshoot-change-tracking-sql-server](/sql/relational-databases/track-changes/cleanup-and-troubleshoot-change-tracking-sql-server) |
+| 22125 | 16 | No | Change tracking autocleanup is currently not able to maintain retention for database ID %d. Number of expired records: %d. If this warning persists, check the following resource: [https://learn.microsoft.com/sql/relational-databases/track-changes/cleanup-and-troubleshoot-change-tracking-sql-server](../../track-changes/cleanup-and-troubleshoot-change-tracking-sql-server.md) |
 | 22201 | 16 | No | Internal error. Unable to acquire the latch holding buffers for DW Tiered Storage ColumnStore Scan. |
 | 22202 | 16 | No | Internal error. Unable to run the remote cs garbage collector. Error Code 22202. |
 | 22203 | 16 | No | Internal error. Unable to update the blobs table in the catalogDB. Error Code 22203. |

docs/relational-databases/errors-events/includes/sql-server-2019-database-engine-events-and-errors-8000-8999.md

@@ -2,7 +2,7 @@
 author: MashaMSFT
 ms.author: mathoma
 ms.reviewer: randolphwest
-ms.date: 02/17/2023
+ms.date: 04/21/2023
 ms.topic: include
 ---
 | Error| Severity | Event logged | Description|
@@ -322,7 +322,7 @@ ms.topic: include
 | 8537 | 16 | No | This transaction was aborted by Kernel Transaction Manager (KTM). |
 | 8538 | 16 | No | The current isolation level is not supported by the FILESTREAM 0x%x. |
 | 8539 | 10 | Yes | The distributed transaction with UOW %ls was forced to commit. MS DTC became temporarily unavailable and forced heuristic resolution of the transaction. This is an informational message only. No user action is required. |
-| 8540 | 10 | Yes | The distributed transaction with UOW %ls was forced to rollback. |
+| 8540 | 10 | Yes | The distributed transaction with UOW %ls was forced to roll back. |
 | 8541 | 10 | Yes | System process ID %d tried to terminate the distributed transaction with Unit of Work ID %ls. This message occurs when the client executes a KILL statement on the distributed transaction. |
 | 8542 | 10 | Yes | Spid %d tried to commit the distributed transaction with UOW %ls. |
 | 8543 | 10 | Yes | Unable to commit a prepared transaction from the Microsoft Distributed Transaction Coordinator (MS DTC). Shutting down server to initiate resource manager (RM) recovery. When the RM recovers, it will query the transaction manager about the outcome of the in-doubt transaction, and commit or roll back accordingly. |

docs/relational-databases/errors-events/includes/sql-server-2022-database-engine-events-and-errors-22000-22999.md

@@ -2,7 +2,7 @@
 author: MashaMSFT
 ms.author: mathoma
 ms.reviewer: randolphwest
-ms.date: 04/06/2023
+ms.date: 04/21/2023
 ms.topic: include
 ---
 | Error| Severity | Event logged | Description|
@@ -50,7 +50,7 @@ ms.topic: include
 | 22122 | 16 | No | Change Tracking autocleanup failed on side table of "%s".  If the failure persists, use sp_flush_CT_internal_table_on_demand to clean up expired records from its side table. |
 | 22123 | 16 | No | Change Tracking autocleanup is blocked on side table of "%s". If the failure persists, check if the table "%s" is blocked by any process . |
 | 22124 | 16 | No | Change Tracking manual cleanup is blocked on side table of "%s". If the failure persists, check if the table "%s" is blocked by any process . |
-| 22125 | 16 | No | Change tracking autocleanup is currently not able to maintain retention for database ID %d. Number of expired records: %d. If this warning persists, check the following resource: [https://learn.microsoft.com/sql/relational-databases/track-changes/cleanup-and-troubleshoot-change-tracking-sql-server](/sql/relational-databases/track-changes/cleanup-and-troubleshoot-change-tracking-sql-server) |
+| 22125 | 16 | No | Change tracking autocleanup is currently not able to maintain retention for database ID %d. Number of expired records: %d. If this warning persists, check the following resource: [https://learn.microsoft.com/sql/relational-databases/track-changes/cleanup-and-troubleshoot-change-tracking-sql-server](../../track-changes/cleanup-and-troubleshoot-change-tracking-sql-server.md) |
 | 22201 | 16 | No | Internal error. Unable to acquire the latch holding buffers for DW Tiered Storage ColumnStore Scan. |
 | 22202 | 16 | No | Internal error. Unable to run the remote cs garbage collector. Error Code 22202. |
 | 22203 | 16 | No | Internal error. Unable to update the blobs table in the catalogDB. Error Code 22203. |

docs/relational-databases/errors-events/includes/sql-server-2022-database-engine-events-and-errors-31000-41399.md

@@ -2,7 +2,7 @@
 author: MashaMSFT
 ms.author: mathoma
 ms.reviewer: randolphwest
-ms.date: 04/06/2023
+ms.date: 04/21/2023
 ms.topic: include
 ---
 > [!NOTE]
@@ -1255,7 +1255,7 @@ ms.topic: include
 | 39018 | 16 | No | Parameter '%.\*ls' uses a data type that is not supported by the runtime for '%.\*s' script. Unsupported types are timestamp, datetime2, datetimeoffset, time, text, ntext, image, hierarchyid, xml, sql_variant and user-defined type. External script request id is %ls. |
 | 39019 | 10 | No | An external script error occurred: %.\*ls%.\*ls |
 | 39020 | 16 | No | Feature 'Advanced Analytics Extensions' is not installed. Please consult Books Online for more information on this feature. |
-| 39021 | 16 | No | Unable to launch runtime for '%.\*s' script for request id: %ls. Please check the configuration of the '%.\*s' runtime. See '[https://learn.microsoft.com/sql/machine-learning/install/sql-machine-learning-services-windows-install-sql-2022](/sql/machine-learning/install/sql-machine-learning-services-windows-install-sql-2022)' for setup instructions. |
+| 39021 | 16 | No | Unable to launch runtime for '%.\*s' script for request id: %ls. Please check the configuration of the '%.\*s' runtime. See '[https://learn.microsoft.com/sql/machine-learning/install/sql-machine-learning-services-windows-install-sql-2022](../../../machine-learning/install/sql-machine-learning-services-windows-install-sql-2022.md)' for setup instructions. |
 | 39022 | 10 | No | STDERR message(s) from external script: %.\*ls%.\*ls |
 | 39023 | 16 | No | 'sp_execute_external_script' is disabled on this instance of SQL Server. Use sp_configure 'external scripts enabled' to enable it. |
 | 39024 | 16 | No | Parallel execution of 'sp_execute_external_script' failed. Specify WITH RESULT SETS clause with output schema. |

docs/relational-databases/errors-events/mssqlserver-3013-database-engine-error.md

@@ -58,9 +58,9 @@ Examine the SQL Error log for other messages that occur alongside this error for
 
 - For database corruption issues, you're likely to observe other errors in SQL Server. Run DBCC CHECKDB to identify any errors in the database and resolve. For more information, see [Troubleshoot database consistency errors reported by DBCC CHECKDB](/troubleshoot/sql/database-engine/database-file-operations/troubleshoot-dbcc-checkdb-errors)
 
-- If your server principal account lacks permissions to do a backup or a restore operation, ensure account that is granted those permissions. See [Backup permissions](/sql/t-sql/statements/backup-transact-sql#permissions) and [Restore permissions](/sql/t-sql/statements/restore-statements-transact-sql#permissions)
+- If your server principal account lacks permissions to do a backup or a restore operation, ensure account that is granted those permissions. See [Backup permissions](../../t-sql/statements/backup-transact-sql.md#permissions) and [Restore permissions](../../t-sql/statements/restore-statements-transact-sql.md#permissions)
 
-- For SQL Server service account permission issues, ensure that the SQL Server service account has read and write access to the backup device or the file system where the backup file is written. See [Backup permissions](/sql/t-sql/statements/backup-transact-sql#permissions). 
+- For SQL Server service account permission issues, ensure that the SQL Server service account has read and write access to the backup device or the file system where the backup file is written. See [Backup permissions](../../t-sql/statements/backup-transact-sql.md#permissions). 
 
 
 Here are examples of commonly observed errors together with 3013.

docs/relational-databases/errors-events/mssqlserver-8645-database-engine-error.md

@@ -28,7 +28,7 @@ helpviewer_keywords:
 
 ## Explanation
 
-This error is raised if a SQL Server request has waited for query execution (QE) memory for an extended period of time and memory wasn't available. Query execution memory is primarily used for sort operations, hash operations, bulk copy operations and index creation and population. A query that performs one of these operations requests a memory grant. If no memory is available, the query is set to wait on a [RESOURCE_SEMAPHORE](/sql/relational-databases/system-dynamic-management-views/sys-dm-os-wait-stats-transact-sql#resource_semaphore) until memory becomes available. If the memory isn't available after over 20 minutes of waiting, then SQL Server terminates the query with error 8645 "A timeout occurred while waiting for memory resources to execute the query in the resource pool 'default'. The timeout value varies slightly between versions of SQL Server. You may see the timeout value set at the server level by looking at `timeout_sec` in [sys.dm_exec_query_memory_grants](/sql/relational-databases/system-dynamic-management-views/sys-dm-exec-query-memory-grants-transact-sql).
+This error is raised if a SQL Server request has waited for query execution (QE) memory for an extended period of time and memory wasn't available. Query execution memory is primarily used for sort operations, hash operations, bulk copy operations and index creation and population. A query that performs one of these operations requests a memory grant. If no memory is available, the query is set to wait on a [RESOURCE_SEMAPHORE](../system-dynamic-management-views/sys-dm-os-wait-stats-transact-sql.md#resource_semaphore) until memory becomes available. If the memory isn't available after over 20 minutes of waiting, then SQL Server terminates the query with error 8645 "A timeout occurred while waiting for memory resources to execute the query in the resource pool 'default'. The timeout value varies slightly between versions of SQL Server. You may see the timeout value set at the server level by looking at `timeout_sec` in [sys.dm_exec_query_memory_grants](../system-dynamic-management-views/sys-dm-exec-query-memory-grants-transact-sql.md).
 
 ## Cause
 

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

@@ -427,7 +427,7 @@ In a deadlock scenario, the victim transaction is automatically stopped and roll
 
 To cause a deadlock, you will need to connect two sessions to the `AdventureWorksLT2019` database. We'll refer to these sessions as **Session A** and **Session B**. You can create these two sessions simply by creating two query windows in SQL Server Management Studio (SSMS).
 
-In **Session A**, run the following Transact-SQL. This code begins an [explicit transaction](/sql/relational-databases/sql-server-transaction-locking-and-row-versioning-guide#starting-transactions) and runs a single statement that updates the `SalesLT.Product` table. To do this, the transaction acquires an [update (U) lock](/sql/relational-databases/sql-server-transaction-locking-and-row-versioning-guide#behavior-when-modifying-data) on one row on table `SalesLT.Product` which is converted to an exclusive (X) lock. We leave the transaction open.
+In **Session A**, run the following Transact-SQL. This code begins an [explicit transaction](sql-server-transaction-locking-and-row-versioning-guide.md#starting-transactions) and runs a single statement that updates the `SalesLT.Product` table. To do this, the transaction acquires an [update (U) lock](sql-server-transaction-locking-and-row-versioning-guide.md#behavior-when-modifying-data) on one row on table `SalesLT.Product` which is converted to an exclusive (X) lock. We leave the transaction open.
 
 ```sql
 BEGIN TRAN
@@ -437,7 +437,7 @@ BEGIN TRAN
 
 ```
 
-Now, in **Session B**, run the following Transact-SQL. This code doesn't explicitly begin a transaction. Instead, it operates in [autocommit transaction mode](/sql/relational-databases/sql-server-transaction-locking-and-row-versioning-guide#starting-transactions). This statement updates the `SalesLT.ProductDescription` table. The update will take out an update (U) lock on 72 rows on the `SalesLT.ProductDescription` table. The query joins to other tables, including the `SalesLT.Product` table.
+Now, in **Session B**, run the following Transact-SQL. This code doesn't explicitly begin a transaction. Instead, it operates in [autocommit transaction mode](sql-server-transaction-locking-and-row-versioning-guide.md#starting-transactions). This statement updates the `SalesLT.ProductDescription` table. The update will take out an update (U) lock on 72 rows on the `SalesLT.ProductDescription` table. The query joins to other tables, including the `SalesLT.Product` table.
 
 ```sql
 UPDATE SalesLT.ProductDescription SET Description = Description