Skip to content

Commit e20327d

Browse files
committed
Merge branch 'master' of https://github.com/MicrosoftDocs/sql-docs-pr into bdc-troubleshooting
2 parents d3cbbbe + 3963fbd commit e20327d

26 files changed

Lines changed: 134 additions & 5 deletions
Lines changed: 46 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,46 @@
1+
---
2+
title: " ADR cleaner retry timeout (min) configuration option | Microsoft Docs"
3+
description: "Explains the SQL Server instance configuration setting for ADR cleaner retry timeout."
4+
ms.custom: ""
5+
ms.date: "06/01/2020"
6+
ms.prod: sql
7+
ms.reviewer: ""
8+
ms.technology: configuration
9+
ms.topic: conceptual
10+
helpviewer_keywords:
11+
- "ADR cleaner retry timeout (min)"
12+
author: MikeRayMSFT
13+
ms.author: mikeray
14+
---
15+
# ADR cleaner retry timeout (min) configuration option
16+
17+
[!INCLUDE[appliesto-ss-xxxx-xxxx-xxx-md](../../includes/appliesto-ss-xxxx-xxxx-xxx-md.md)]
18+
19+
Introduced in SQL Server 2019.
20+
21+
This configuration setting is required for [accelerated database recovery](../../relational-databases/accelerated-database-recovery-concepts.md). The cleaner is the asynchronous process that wakes up periodically and cleans page versions that are not needed.
22+
23+
Occasionally the cleaner runs into issues while acquiring object level locks due to conflicts with user workload during its sweep. It tracks such pages in a separate list. The ADR cleaner retry timeout (default value of 15) controls the amount of time the cleaner would spend exclusively retrying object lock acquisition and cleanup of page before abandoning the sweep. Completion of a sweep with 100% success is essential to keep the growth of aborted transactions in the aborted transactions map. If the separate list cannot be cleaned up in the prescribed timeout, then the current sweep will be abandoned and the next sweep will start.
24+
25+
## Remarks
26+
27+
The cleaner is single threaded in SQL Server 2019 and so one SQL Server instance can work on one database at a time. If the instance has more than one user database with ADR enabled, then do not increase the timeout to a large value as that could delay cleanup on one database while the retry is happening on another database.
28+
29+
## Examples
30+
31+
The following examples sets the cleaner retry timeout.
32+
33+
```tsql
34+
sp_configure 'show advanced options', 1;
35+
RECONFIGURE;
36+
GO
37+
sp_configure 'ADR cleaner retry timeout', 15;
38+
RECONFIGURE;
39+
GO
40+
```
41+
42+
## See Also
43+
44+
- [Server Configuration Options (SQL Server)](../../database-engine/configure-windows/server-configuration-options-sql-server.md)
45+
- [Accelerated database recovery](../../relational-databases/accelerated-database-recovery-concepts.md)
46+
- [Manage accelerated database recovery](../../relational-databases/accelerated-database-recovery-management.md)
Lines changed: 55 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,55 @@
1+
---
2+
title: "ADR Preallocation Factor configuration option | Microsoft Docs"
3+
description: "Explains the SQL Server instance configuration setting for ADR Preallocation Factor."
4+
ms.custom: ""
5+
ms.date: "06/01/2020"
6+
ms.prod: sql
7+
ms.reviewer: ""
8+
ms.technology: configuration
9+
ms.topic: conceptual
10+
helpviewer_keywords:
11+
- "ADR Preallocation Factor"
12+
author: MikeRayMSFT
13+
ms.author: mikeray
14+
---
15+
# ADR Preallocation Factor configuration option
16+
17+
[!INCLUDE[appliesto-ss-xxxx-xxxx-xxx-md](../../includes/appliesto-ss-xxxx-xxxx-xxx-md.md)]
18+
19+
Introduced in SQL Server 2019.
20+
21+
This configuration setting is required for [accelerated database recovery](../../relational-databases/accelerated-database-recovery-concepts.md).
22+
23+
Accelerated Database Recovery (ADR) maintains versions of data for recovery purposes. These versions are generated as part of various data manipulation language (DML) operations. Versions are stored in an internal table called persistent version store (PVS).
24+
25+
## Remarks
26+
27+
Performance can degrade if pages are allocated for the PVS table as part of foreground user DML operations. To address this, there is a background thread which pre-allocates pages and keeps them readily available for DML transactions. Performance is best when the background thread preallocates enough pages and the percentage of foreground PVS allocations is close to 0. The error log contains entires with the tag `PreallocatePVS` if the percentage goes high and is affecting performance.
28+
29+
The number of pages the background thread pre-allocates is based on various workload heuristics, but largely allocates pages in chunks of 512 pages. The ADR preallocation factor is a multiple of the chunk. By default, the factor is 4. This means it preallocates 2048 pages at once when required.
30+
31+
While the background thread takes workload patterns into consideration, this factor can be increased if necessary to improve performance.
32+
33+
> [!CAUTION]
34+
> If PVS preallocation is increased too much, it will contend with other allocations in the system and might actually reduce overall performance
35+
>
36+
> Before you modify this setting, test the overall performance of the system.
37+
38+
## Examples
39+
40+
The following example sets the preallocation factor to 4.
41+
42+
```tsql
43+
sp_configure 'show advanced options', 1;
44+
RECONFIGURE;
45+
GO
46+
sp_configure 'ADR Preallocation Factor', 4;
47+
RECONFIGURE;
48+
GO
49+
```
50+
51+
## See Also
52+
53+
- [Server Configuration Options (SQL Server)](../../database-engine/configure-windows/server-configuration-options-sql-server.md)
54+
- [Accelerated database recovery](../../relational-databases/accelerated-database-recovery-concepts.md)
55+
- [Manage accelerated database recovery](../../relational-databases/accelerated-database-recovery-management.md)

docs/database-engine/configure-windows/server-configuration-options-sql-server.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -68,6 +68,8 @@ Self-configuring options are those that [!INCLUDE[ssNoVersion](../../includes/ss
6868
|[access check cache bucket count](../../database-engine/configure-windows/access-check-cache-server-configuration-options.md) (A)|0|16384|0|
6969
|[access check cache quota](../../database-engine/configure-windows/access-check-cache-server-configuration-options.md) (A)|0|2147483647|0|
7070
|[ad hoc distributed queries](../../database-engine/configure-windows/ad-hoc-distributed-queries-server-configuration-option.md) (A)|0|1|0|
71+
|[ADR cleaner retry timeout (min)](../../database-engine/configure-windows/adr-cleaner-retry-timeout-configuration-option.md)<br><br> Introduced in SQL Server 2019|0|32767|15|
72+
|[ADR Preallocation Factor](../../database-engine/configure-windows/adr-preallocation-factor-server-configuration-option.md)<br><br> Introduced in SQL Server 2019|0|32767|4|
7173
|[affinity I/O mask](../../database-engine/configure-windows/affinity-input-output-mask-server-configuration-option.md) (A, RR)|-2147483648|2147483647|0|
7274
|[affinity64 I/O mask](../../database-engine/configure-windows/affinity64-input-output-mask-server-configuration-option.md) (A, only available on 64-bit version of [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)])|-2147483648|2147483647|0|
7375
|[affinity mask](../../database-engine/configure-windows/affinity-mask-server-configuration-option.md) (A)|-2147483648|2147483647|0|
@@ -118,6 +120,7 @@ Self-configuring options are those that [!INCLUDE[ssNoVersion](../../includes/ss
118120
|[open objects](../../database-engine/configure-windows/open-objects-server-configuration-option.md) (A, RR, obsolete)|0|2147483647|0|
119121
|[optimize for ad hoc workloads](../../database-engine/configure-windows/optimize-for-ad-hoc-workloads-server-configuration-option.md) (A)|0|1|0|
120122
|[PH_timeout](../../database-engine/configure-windows/ph-timeout-server-configuration-option.md) (A)|1|3600|60|
123+
|[polybase network encryption](../../relational-databases/polybase/polybase-installation.md#enable) | 0|1 |1
121124
|[polybase enabled](../../relational-databases/polybase/polybase-installation.md#enable) (RR) **Applies to**: [!INCLUDE[sssqlv15](../../includes/sssqlv15-md.md)])|0|1|0|
122125
|[precompute rank](../../database-engine/configure-windows/precompute-rank-server-configuration-option.md) (A)|0|1|0|
123126
|[priority boost](../../database-engine/configure-windows/configure-the-priority-boost-server-configuration-option.md) (A, RR)|0|1|0|

docs/relational-databases/accelerated-database-recovery-concepts.md

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
22
title: "Accelerated database recovery | Microsoft Docs"
3-
ms.date: "08/12/2019"
3+
ms.date: "05/20/2020"
44
ms.prod: sql
55
ms.prod_service: backup-restore
66
ms.technology: backup-restore
@@ -129,7 +129,9 @@ The following types of customers should consider enabling ADR:
129129
- Customers that have seen cases where active transactions are causing the transaction log to grow significantly.
130130
- Customers that have experienced long periods of database unavailability due to SQL Server long running recovery (such as unexpected SQL Server restart or manual transaction rollback).
131131

132+
>[!IMPORTANT]
133+
>ADR is not supported for databases enrolled in database mirroring.
132134
133135
## See Also
134136

135-
137+
[Manage accelerated database recovery](accelerated-database-recovery-management.md)

docs/relational-databases/data-collection/configure-the-management-data-warehouse-sql-server-management-studio.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,6 @@
11
---
22
title: "Configure the Management Data Warehouse (SSMS)"
3+
description: Learn how to configure the management data warehouse to support data storage on one or more instances of SQL Server that are using the data collector.
34
ms.custom: ""
45
ms.date: "03/14/2017"
56
ms.prod: sql

docs/relational-databases/data-collection/data-collection.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,6 @@
11
---
22
title: "Data Collection | Microsoft Docs"
3+
description: Learn introductory information about the data collector, a component of SQL Server 2019 that collects different sets of data.
34
ms.custom: ""
45
ms.date: "07/18/2016"
56
ms.prod: sql

docs/relational-databases/data-collection/management-data-warehouse.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,6 @@
11
---
22
title: "Management Data Warehouse | Microsoft Docs"
3+
description: The management data warehouse in SQL Server is a relational database that contains the data that is collected from a target server.
34
ms.custom: ""
45
ms.date: "03/14/2017"
56
ms.prod: sql

docs/relational-databases/data-collection/system-data-collection-set-reports.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,6 @@
11
---
22
title: "System Data Collection Set Reports | Microsoft Docs"
3+
description: The data collector provides a report for each of the System Data collection sets for monitoring system capacity and system performance in SQL Server.
34
ms.custom: ""
45
ms.date: "03/14/2017"
56
ms.prod: sql

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

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,6 @@
11
---
22
title: "Database Engine Error Severities | Microsoft Docs"
3+
description: Use this list of severity levels to understand the type of problem that SQL Server encountered when the SQL Server Database Engine raises an error.
34
ms.custom: ""
45
ms.date: "03/16/2017"
56
ms.prod: sql

docs/relational-databases/errors-events/database-engine-events-and-errors.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,6 @@
11
---
22
title: "Database engine events and errors"
3+
description: Consult this MSSQL error code list to find explanations for error messages for SQL Server database engine events.
34
ms.custom: ""
45
ms.date: 01/28/2020
56
ms.prod: sql

0 commit comments

Comments
 (0)