Applies ToSQL Server 2014 Enterprise - duplicate (do not use) SQL Server 2014 Enterprise Core - duplicate (do not use) SQL Server 2016 Service Pack 1 SQL Server 2016 Developer - duplicate (do not use) SQL Server 2016 Enterprise - duplicate (do not use) SQL Server 2016 Enterprise Core - duplicate (do not use) SQL Server 2016 Standard - duplicate (do not use)

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.

Facebook LinkedIn Email
SUBSCRIBE RSS FEEDS

Need more help?

Want more options?

Discover Community

Explore subscription benefits, browse training courses, learn how to secure your device, and more.

Microsoft 365 subscription benefits

Microsoft 365 training

Microsoft security

Accessibility center

Communities help you ask and answer questions, give feedback, and hear from experts with rich knowledge.

Ask the Microsoft Community

Microsoft Tech Community

Windows Insiders

Microsoft 365 Insiders