Symptoms
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.
Resolution
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
Each new cumulative update for SQL Server contains all the hotfixes and all the security fixes that were included with the previous cumulative update. Check out the latest cumulative updates for SQL Server:
Latest cumulative update for SQL Server 2016
Latest cumulative update for SQL Server 2017
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
Service packs are cumulative. Each new service pack contains all the fixes that are in previous service packs, together with any new fixes. Our recommendation is to apply the latest service pack and the latest cumulative update for that service pack. You do not have to install a previous service pack before you install the latest service pack. Use Table 1 in the following article for finding more information about the latest service pack and latest cumulative update.
How to determine the version, edition and update level of SQL Server and its components
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
References
Learn about the terminology that Microsoft uses to describe software updates.
