When you rebuild an index for a table in Microsoft SQL Server 2012 or SQL Server 2014, SQL Cache Memory may decrease and CPU utilization increases. Additionally, SQL Server may experience out-of-memory errors.
This issue occurs because much memory is consumed by the MEMORYCLERK_SQLLOGPOOL memory clerk that is used internally for transaction log activities.
Note This issue only occurs when you use AlwaysOn availability groups in SQL Server 2012 or SQL Server 2014.
The issue was first fixed in the following cumulative update of SQL Server.
Cumulative Update 2 for SQL Server 2012 SP2 /en-us/help/2983175
Cumulative Update 1 for SQL Server 2014 /en-us/help/2931693
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:
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
For more information about the similar issue that is described in hotfix 2821783, click the following number to view the article in the Microsoft Knowledge Base:
2821783 FIX: Out-of-memory errors related to a memory clerk in SQL Server 2012