THE SQL Server Blog Spot on the Web

Welcome to - The SQL Server blog spot on the web Sign in | |
in Search

Damian Widera

Memory leak occurs when you run DBCC CHECKDB against a database in SQL Server 2014 - fixed in SQL Server 2014 CU6

Great news today!

At the end of January it was a Connect item  ( that described a possible memory leak on the SQL Server 2014.

The details are as follow: 

sys.dm_os_memory_clerks for type = MEMORYCLERK_SQLQUERYEXEC and sys.dm_os_memory_objects for type = MEMOBJ_COLUMNBATCH show ever increasing values when columnstore tables are integrity checked. For example, if you run DBCC CHECKDB on a database that contains columnstore tables or you run DBCC CHECKTABLE on a columnstore table you will find that the memory shown for the above mentioned clerk and object types is ever increasing.  

The good news is that the problem is fixed and the solution will be available in the SQL Server 2014 CU6. Find more details: 





Published Thursday, February 19, 2015 10:31 AM by Damian
Filed under: ,

Comment Notification

If you would like to receive an email when updates are made to this post, please register here

Subscribe to this post's comments using RSS



George Walkey said:

Ive encountered this on checking over 675 Databases with physical_only taking over 24 hours...when its done, all my RAM is used and my machine so sluggish I need a reboot (SQL does not give back it for some reason, not .net GC memory I assume)

February 19, 2015 6:48 AM

Damian said:

Well, that is why the connect item was created. However no one expected such behaviour on diagnostic procedure :)

February 19, 2015 7:25 AM

Leave a Comment

Privacy Statement