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

Support

Log på

Log på med Microsoft

Log på, eller opret en konto.

Hej

Markér en anden konto.

Du har flere konti

Vælg den konto, du vil logge på med.

Engelsk

Vi beklager. Denne artikel er ikke tilgængelig på dit sprog.

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) Flere...Mindre

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

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

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 terminologythat Microsoft uses to describe software updates.