| author | MashaMSFT |
|---|---|
| ms.author | mathoma |
| ms.reviewer | randolphwest |
| ms.date | 03/06/2026 |
| ms.service | azure-sql-managed-instance |
| ms.topic | include |
For SQL Server 2019 and later versions, enable accelerated database recovery, and ensure the persistent version store (PVS) is set to PRIMARY. If accelerated database recovery isn't enabled on the source SQL Server database, you can't enable it on the target SQL managed instance after the database is migrated. If the persistent version store (PVS) isn't set to PRIMARY, you can experience issues with restore operations on the target SQL managed instance.
For SQL Server 2017 and earlier versions, accelerated database recovery isn't supported, so this step isn't necessary.
To configure accelerated database recovery properly on the source SQL Server database, follow these steps:
-
Enable accelerated database recovery by running the following Transact-SQL script on SQL Server:
ALTER DATABASE [<database name>] SET ACCELERATED_DATABASE_RECOVERY = ON;
-
The persistent version store (PVS) must be set to
PRIMARYon the source database, which is the default configuration. If this was changed previously, you must change it back to PRIMARY before starting the migration.
Service Broker is enabled by default for all versions of SQL Server. If Service Broker was disabled and you plan to use it on SQL Managed Instance, enable Service Broker on the source SQL Server database before you migrate to SQL Managed Instance. If Service Broker isn't enabled on the source SQL Server database, you can't use it on the target SQL managed instance.
To check if Service Broker is enabled, run the following Transact-SQL script on SQL Server instance:
SELECT name AS [Database Name], is_broker_enabled AS [Service Broker Enabled]
FROM sys.databases
WHERE name = '<database name>';If Service Broker is disabled, enable it by running the following Transact-SQL script on the source SQL Server database:
USE master;
GO
ALTER DATABASE [<database name>]
SET ENABLE_BROKER;
GO