I've just posted a Connect item for 'Memory leak when columnstore tables are integrity checked'.
I'm wondering if anyone else who uses big columnstore tables and runs integrity checks every day is encountering the same issue that I've mentioned in the Connect item.
Worst case is that after a number of days of uptime the memory leak gets so bad that select queries are starved of resource pool memory and start throwing memory errors.
This is reproduced for SQL Server 2014 using the latest Cumulative Update (CU5).
Thanks.