FIX: LogPool cache MEMORYCLERK_SQLLOGPOOL consumes more memory when you do online transactions in SQL Server 2016 SP1 Express Edition

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

Symptoms


Assume that you have an in-memory Online Transaction Processing (OLTP) table in Microsoft SQL Server 2016 Service Pack 1 (SP1) Express Edition. You may notice that the LogPool cache memory (the MEMORYCLERK_SQLLOGPOOL memory clerk) consumption grows very large (for example, more than 1 GB) when you perform online transactions.

Note You can monitor the memory consumption of the LogPool cache by using the Log Pool Memory (KB) performance counter that's available under Memory Manager.

Resolution


Service pack information for SQL Server 2016

This issue is fixed in the following service pack for SQL Server:

       Service Pack 2 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 terminology that Microsoft uses to describe software updates.