FIX: A REDO thread is not available in the secondary replica after an availability database is dropped in SQL Server

Applies to: SQL Server 2012 EnterpriseSQL Server 2012 DeveloperSQL Server 2012 Enterprise Core


Assume that you use Microsoft SQL Server Always On Availability Groups. When you try to drop a database that's part of an availability group, you receive the expected error message 3752. After that occurs, the transaction log redo thread at the secondary may stop until you restart the database. Or, it may suspend and resume data movement for this Availability Group.


Cumulative Update Information for SQL Server:

This problem is fixed in  the following cumulative updates for SQL Server:

       Cumulative update 8 for SQL Server 2016 SP1  

       Cumulative Update 4 for SQL Server 2017

       Cumulative update 10 for SQL Server 2014 SP2

       Cumulative Update 9 for SQL Server 2012 Service Pack 3

Service Pack Information for SQL Server:

This issue is fixed in the following service pack for SQL Server:

       Service Pack 4 for SQL Server 2012

For more information about how to obtain the latest service pack, see How to obtain the latest service pack for SQL Server 2012


Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.


Learn about the terminology that Microsoft uses to describe software updates.