FIX: Always On database is stuck at “Recovery Pending” after the host name of an availability replica is renamed in SQL Server

Gilt für: SQL Server 2017 DeveloperSQL Server 2017 EnterpriseSQL Server 2017 Enterprise Core


Assume that you use Always On Availability Groups (AG) in Microsoft SQL Server. When you rename the host name of the server that hosts the instance of SQL Server and restart the instance, all databases in the AG remain in RECOVERY_PENDING state, and access violations occur.


This fix is included in the following update for SQL Server:

Cumulative Update 8 for SQL Server 2017


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


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