| title | sys.sp_persistent_version_cleanup (Transact-SQL) | ||||
|---|---|---|---|---|---|
| description | Manually starts persistent version store (PVS) cleanup process, a key element of accelerated database recovery (ADR). | ||||
| author | rwestMSFT | ||||
| ms.author | randolphwest | ||||
| ms.reviewer | dfurman | ||||
| ms.date | 10/19/2025 | ||||
| ms.service | sql | ||||
| ms.subservice | system-objects | ||||
| ms.topic | reference | ||||
| ms.custom |
|
||||
| f1_keywords |
|
||||
| dev_langs |
|
||||
| monikerRange | >=sql-server-ver15 || >=sql-server-linux-ver15 || =azuresqldb-mi-current || =azuresqldb-current || =fabric-sqldb |
[!INCLUDE SQL Server 2019, ASDB, ASDBMI-fabricsqldb]
Manually starts persistent version store (PVS) cleanup process, a key element of accelerated database recovery (ADR). This cleaner also removes uncommitted data in PVS from aborted transactions.
It isn't typically necessary to start the PVS cleanup process manually using sys.sp_persistent_version_cleanup. However in some scenarios, you might want to initiate the PVS cleanup process manually during a known period of rest/recovery after busy OLTP activity.
For more information about ADR, see Accelerated database recovery.
:::image type="icon" source="../../includes/media/topic-link-icon.svg" border="false"::: Transact-SQL syntax conventions
sp_persistent_version_cleanup
[ [ @dbname = ] N'dbname' ]
[ , [ @scanallpages = ] scanallpages ]
[ , [ @clean_option = ] clean_option ]
[ ; ]
Optional. The name of the database to clean up. If not provided, uses the current database context. @dbname is sysname, with a default of NULL.
Optional. @scanallpages is bit, with a default of 0. When set to 1, this option forces clean up of all database pages even if not versioned.
Optional. Possible options determine whether or not to reclaim off-row PVS page. @clean_option is int, with a default of 0. This reference isn't commonly needed and the default value 0 is recommended.
| Value | Description |
|---|---|
0 |
Default, no option specified |
1 |
off-row version store without checking individual PVS page contents |
2 |
off-row version store with each PVS page visited |
3 |
in-row version store only |
4 |
internal use only |
0 (success) or 1 (failure).
None.
Requires the ALTER permission on the database.
The sys.sp_persistent_version_cleanup stored procedure is synchronous, meaning that it doesn't complete until all version information is cleaned up from the current PVS.
In [!INCLUDE sssql19-md], the PVS cleanup process only executes for one database at a time. In Azure SQL Database and Azure SQL Managed Instance, and beginning with [!INCLUDE sssql22-md], the PVS cleanup process can execute in parallel against multiple databases in the same instance.
If the PVS cleanup process is already running against the desired database, this stored procedure is blocked before starting another PVS cleanup process. Active, long-running transactions in any database on the same database engine instance that have ADR enabled can also block PVS cleanup.
You can monitor the version cleaner task by looking for its process with the following sample query:
SELECT *
FROM sys.dm_exec_requests
WHERE command LIKE '%PERSISTED_VERSION_CLEANER%';An active transaction might prevent the PVS cleanup process from starting. If this occurs, the session running the sys.sp_persistent_version_cleanup stored procedure waits with the PVS_CLEANUP_LOCK wait type. You can wait for the transaction to complete, or you can consider killing the blocker session with an active transaction, if possible.
If ADR is disabled, run sys.sp_persistent_version_cleanup to clean up previous versions still in the PVS.
To activate the PVS cleanup process manually between workloads or during maintenance windows, use the following sample script:
EXECUTE sys.sp_persistent_version_cleanup [database_name];For example:
EXECUTE sys.sp_persistent_version_cleanup [WideWorldImporters];Or, to assume the current database context:
USE [WideWorldImporters];
GO
EXECUTE sys.sp_persistent_version_cleanup;