Symptoms

Assume that you have an Always On Availability Group (AG) that has many databases in Microsoft SQL Server 2019 or 2016. During a SQL Server restart, a replica disconnection, or AG failover, you notice that the volume of the log line for DbMgrPartnerCommitPolicy::SetSyncAndRecoveryPoint is extremely high and causes unnecessary CPU usage.

Status

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

Resolution

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

Each new cumulative update for SQL Server contains all the hotfixes and security fixes that were in the previous build. We recommend that you install the latest build for your version of SQL Server:

Latest cumulative update for SQL Server 2019

Service pack information for SQL Server 2016

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

Service packs are cumulative. Each new service pack contains all the fixes that are in previous service packs, together with any new fixes. We recommend that you 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 to find more information about the latest service pack and latest cumulative update.

Determine the version, edition, and update level of SQL Server and its components

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!

×