FIX: Parallel redo causes high memory usage in SQL Server 2016 when it's compared to SQL Server 2014 or earlier versions

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

Symptoms


Microsoft SQL Server 2016 may cause higher memory usage in the MEMORYCLERK_SQLSTORENG memory clerk, when you compare it with SQL Server 2014 or earlier versions. This issue is more severe when large number of databases exist on an instance of SQL Server 2016. This is caused by a memory leak in parallel redo during database startup or server startup.

Resolution


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

       Cumulative Update 3 for SQL Server 2016 SP1

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.