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

Applies to: SQL Server 2016 DeveloperSQL Server 2016 EnterpriseSQL Server 2016 Enterprise Core


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.


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.