Database Mirroring cannot be set for database 'ADR_Mirroring ' because the database has Accelerated Database Recovery enabled or there are still versions in the Persisted Version Store. If Accelerated Database Recovery is disabled, please run sys.sp_persistent_version_cleanup '<DatabaseName>' to clean up previous versions..

KB4042251 - FIX: Database mirroring failover fails with error 3456 in SQL Server 2016 or 2017 - Microsoft Support. SQL Server 2016 Enterprise Core - duplicate (do not use) More... Symptoms. You set up database mirroring by using Microsoft SQL Server 2016 or 2017.

The mirroring connection to "<server network address>" has timed out for database "<database name>" after 60 seconds without a response. Check the service and network connections. Resolution. This issue is fixed in the following cumulative update for SQL Server: Cumulative Update 3 for SQL Server 2017. About cumulative updates for SQL Server:

When you use database mirroring in Microsoft SQL Server 2012 or Microsoft SQL Server 2014, you may hit an assert condition and database mirroring enters to suspended state. Cause. The issue occurs because, when allocating a new page, SQL Server obtains an X lock on the new page.

KB2403218 - FIX: Database mirroring session is suspended in SQL Server 2005 and in SQL Server 2008 and in SQL Server 2008 R2 if the High-performance (asynchronous) mode is used - Microsoft Support. Microsoft SQL Server 2005 Enterprise Edition More...

KB4042251 - FIX: Database mirroring failover fails with error 3456 in SQL Server 2016 or 2017 - Microsoft Support. SQL Server 2016 Enterprise Core - duplicate (do not use) More... Symptoms. You set up database mirroring by using Microsoft SQL Server 2016 or 2017.

Summary. This update enables you to use Microsoft SQL Server 2017 Express edition as a witness role in a database mirroring session. More information. This update is included in Cumulative Update 1 for SQL Server 2017. About SQL Server 2017 builds.

You configure database mirroring for a database on a computer that is running SQL Server 2008 R2 or SQL Server 2008. You enable change tracking on this database. The database automatically fails over, and then the mirrored database becomes the principal database.

KB3177238 - FIX: No automatic failover after database mirroring stops unexpectedly in SQL Server - Microsoft Support. SQL Server 2012 Business Intelligence SQL Server 2012 Developer More... Symptoms. Assume that you set up a database mirroring session in SQL Server 2012,2014 or 2016. You add a witness to support automatic failover.

Fixes an issue in which a rolling upgrade for an AlwaysOn replica or a database mirroring instance fails after Cumulative Update 1 for SQL Server 2016 is installed.