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


This issue 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


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


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?

Any additional feedback? (Optional)

Thank you for your feedback!