Symptoms

In a SQL Server Always On environment, you start a large transaction on the primary replica. If a new page is allocated by a page split in the transaction, a PAGE IX lock migrates to this new page on the secondary replica. In this situation, a conflict with a PAGE X lock occurs, and a deadlock condition causes a deferred transaction in the secondary replica.

Resolution

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

    Cumulative Update 5 for SQL Server 2016 RTM

    Cumulative Update 2 for SQL Server 2016 SP1

     Cumulative Update 3 for SQL Server 2014 Service Pack 2
  

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 2016

Latest cumulative update for SQL Server 2014

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!

×