KB3154226 - FIX: Memory leak on the AlwaysOn secondary replica when change tracking is enabled in SQL Server

Applies To
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) SQL Server 2014 Developer - duplicate (do not use) SQL Server 2014 Enterprise - duplicate (do not use) SQL Server 2014 Standard - duplicate (do not use) SQL Server 2014 Web - duplicate (do not use) SQL Server 2012 Developer SQL Server 2012 Enterprise SQL Server 2012 Standard

Symptoms

Assume that you use the AlwaysOn Availability Groups feature in Microsoft SQL Server. If you enable change tracking for a database that's in the availability group, a memory leak may occur on the secondary replica.

The memory leak is reported under MEMORYCLERK_SQLSTORENG memory clerk and the MEMOBJ_PERDATABASE memory object. You can query these values from the DMV sys.dm_os_memory_clerks and sys.dm_os_memory_objects.

Resolution

The issue was first fixed in the following cumulative updates of SQL Server:

Recommendation: Install the latest cumulative update for SQL Server

Each new cumulative update for SQL Server contains all the hotfixes and all the security fixes that were included with the previous cumulative update. We recommend that you download and install the latest cumulative updates for SQL Server:

      

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.