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

Symptoms

Consider the following scenario:

  • You enable change tracking for a database in an instance of SQL Server 2014.

  • The instance of SQL Server shuts down unexpectedly. For example, the operating system crashes.

  • You restart the instance of SQL Server.

In this scenario, the sys.dm_tran_commit_table DMV and the CHANGETABLE function returns incorrect results, or it is missing some records.

Resolution

This issue is fixed in Cumulative Update 4 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 2014.

WorkaroundTo work around this issue, turn on the AUTO_CLOSE database option for the databases that have change tracking enabled.

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

References

Recommendations and guidelines for setting the AUTO_CLOSE database option in SQL Server

Learn about the terminology 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