Make ADR config settings applicable to SQL MI (#35937)

Author: dimitri-furman

docs/database-engine/configure-windows/adr-cleaner-retry-timeout-configuration-option.md

@@ -4,18 +4,18 @@ description: "Explains the SQL Server instance configuration setting for ADR cle
 author: MikeRayMSFT
 ms.author: mikeray
 ms.reviewer: randolphwest
-ms.date: 08/26/2025
+ms.date: 11/25/2025
 ms.service: sql
 ms.subservice: configuration
-ms.topic: conceptual
+ms.topic: article
 helpviewer_keywords:
   - "ADR cleaner retry timeout (min)"
 ---
 # Server configuration: ADR cleaner retry timeout (min)
 
-[!INCLUDE [SQL Server](../../includes/applies-to-version/sqlserver.md)]
+[!INCLUDE [sqlserver2019-asdbmi](../../includes/applies-to-version/sqlserver2019-asdbmi.md)]
 
-[!INCLUDE [sssql19-starting-md](../../includes/sssql19-starting-md.md)], this configuration setting is used for [accelerated database recovery](../../relational-databases/accelerated-database-recovery-concepts.md) (ADR). The cleaner is an asynchronous process that wakes up periodically and cleans row versions that aren't needed.
+Starting in [!INCLUDE [sssql19-md](../../includes/sssql19-md.md)], and in [!INCLUDE [ssazuremi-md](../../includes/ssazuremi-md.md)], this configuration setting is used for [accelerated database recovery](../../relational-databases/accelerated-database-recovery-concepts.md) (ADR). The cleaner is an asynchronous process that wakes up periodically and cleans row versions that aren't needed.
 
 Occasionally the cleaner might run into issues while acquiring object or partition level `IX` locks due to lock conflicts with user workloads during its sweep. The cleaner tracks such pages in a separate list. `ADR cleaner retry timeout (min)` controls the amount of time the cleaner spends exclusively retrying `IX` lock acquisition and cleanup of pages before it abandons the sweep. Completing the sweep with 100% success is essential to keep the growth of aborted transactions in the aborted transactions map. If the pages on the separate list can't be cleaned up in the prescribed time-out, then the current sweep is abandoned, and the cleanup is attempted during the next sweep.
 

docs/database-engine/configure-windows/adr-cleaner-thread-count-configuration-option.md

@@ -4,18 +4,18 @@ description: "Explains the SQL Server instance configuration setting for ADR cle
 author: MikeRayMSFT
 ms.author: mikeray
 ms.reviewer: randolphwest, dfurman
-ms.date: 08/26/2025
+ms.date: 11/25/2025
 ms.service: sql
 ms.subservice: configuration
-ms.topic: conceptual
+ms.topic: article
 helpviewer_keywords:
   - "ADR cleaner thread count"
 ---
 # Server configuration: ADR Cleaner Thread Count
 
-[!INCLUDE [sqlserver2022-and-later](../../includes/applies-to-version/sqlserver2022-and-later.md)]
+[!INCLUDE [sqlserver2022-asmi](../../includes/applies-to-version/sqlserver2022-asmi.md)]
 
-This configuration setting is used for [accelerated database recovery](../../relational-databases/accelerated-database-recovery-concepts.md) (ADR). The cleaner is an asynchronous process that wakes up periodically and cleans page versions that aren't needed.
+Starting in [!INCLUDE [sssql22-md](../../includes/sssql22-md.md)], and in [!INCLUDE [ssazuremi-md](../../includes/ssazuremi-md.md)], this configuration setting is used for [accelerated database recovery](../../relational-databases/accelerated-database-recovery-concepts.md) (ADR). The cleaner is an asynchronous process that wakes up periodically and cleans page versions that aren't needed.
 
 By default, this configuration setting is set to `1`. This means that the cleaner uses a single thread to clean persistent version store (PVS) in all databases on the database engine instance.
 

docs/database-engine/configure-windows/adr-preallocation-factor-server-configuration-option.md

@@ -4,19 +4,18 @@ description: "Explains the SQL Server instance configuration setting for ADR pre
 author: MikeRayMSFT
 ms.author: mikeray
 ms.reviewer: randolphwest, dfurman
-ms.date: 08/26/2025
+ms.date: 11/25/2025
 ms.service: sql
 ms.subservice: configuration
-ms.topic: conceptual
+ms.topic: article
 helpviewer_keywords:
   - "ADR Preallocation Factor"
 ---
-
 # Server configuration: ADR Preallocation Factor
 
-[!INCLUDE [SQL Server](../../includes/applies-to-version/sqlserver.md)]
+[!INCLUDE [sqlserver2019-asdbmi](../../includes/applies-to-version/sqlserver2019-asdbmi.md)]
 
-[!INCLUDE [sssql19-starting-md](../../includes/sssql19-starting-md.md)], this configuration setting is used by [accelerated database recovery](../../relational-databases/accelerated-database-recovery-concepts.md).
+Starting in [!INCLUDE [sssql19-md](../../includes/sssql19-md.md)], and in [!INCLUDE [ssazuremi-md](../../includes/ssazuremi-md.md)], this configuration setting is used by [accelerated database recovery](../../relational-databases/accelerated-database-recovery-concepts.md).
 
 Accelerated database recovery (ADR) uses row versions for transaction management and database recovery purposes. These versions are generated as part of various data manipulation language (DML) operations. Versions are stored either in-row, or off-row in an internal table called the persistent version store (PVS).
 

docs/includes/applies-to-version/sqlserver2019-asdbmi.md

@@ -1,9 +1,9 @@
 ---
-author: rothja
-ms.author: jroth
-ms.date: 08/06/2020
+author: rwestMSFT
+ms.author: randolphwest
+ms.date: 11/26/2025
 ms.service: sql
 ms.topic: include
 ---
 
-[!INCLUDE [Applies to](../../includes/applies-md.md)] [!INCLUDE [SQL Server 2019](_ss2019.md)] [!INCLUDE [SQL Managed Instance](../../includes/applies-to-version/_asmi.md)]
+[!INCLUDE [Applies to](../../includes/applies-md.md)] [!INCLUDE [SQL Server 2019](_ss2019.md)] and later versions [!INCLUDE [SQL Managed Instance](../../includes/applies-to-version/_asmi.md)]