KB4459900 - FIX: Synchronization fails when you stop primary replica and fail over a secondary replica to primary in Read-Scale AG in SQL Server 2017

Support

Hello,

Select a different account.

You have multiple accounts

Choose the account you want to sign in with.

Applies To

SQL Server 2017 Developer on Windows SQL Server 2017 Enterprise on Windows SQL Server 2017 Enterprise Core on Windows SQL Server 2017 Standard on Windows

Symptoms

Assume that you use Read-Scale Availability Group (AG), for example "CLUSTER_TYPE = NONE" in SQL Server 2017. If you stop the primary replica and fail over a synchronous mode secondary replica to primary, synchronization will be failed. Additionally, you will receive Not Synchronizing message from new primary AG database.

Note: This issue does not occur in SQL Server 2017 RTM.

Resolution

This issue is fixed in the following cumulative update for SQL Server:

Cumulative Update 11 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 2017

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 terminologythat Microsoft uses to describe software updates.