Symptoms

If you use distributed availability groups, some availability databases are not fully started after you restart the server instance of Microsoft SQL Server 2016.

Resolution

The issue was first fixed in the following cumulative update of SQL Server:

Each new cumulative update for SQL Server contains all the hotfixes and all the security fixes that were included with the previous cumulative update. We recommend that you download and install the latest cumulative updates for SQL Server:


More Information

Cause:

After you restart the server instance, a role change event that was published during the online process is affected by a logical timestamp change. The original event that was published by the transition from "primary pending" to "primary normal" is changed by the transition from "primary normal" to "global primary." However, the transition from "primary normal" to "global primary" does not publish the event to the DBR subscriber. Therefore, some databases are not fully started. This issue applies only to distributed availability groups. If you are not using distributed availability groups, this issue should not affect you.

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.

Need more help?

Expand your skills
Explore Training
Get new features first
Join Microsoft Insiders

Was this information helpful?

What affected your experience?

Thank you for your feedback!

×