Unexpected behaviour when using columnstore index | Microsoft Connect
An item has very recently been published to the Microsoft Connect website with regards to an issue relating to Clustered Columnstore Indexes.
Unexpected behaviour when using columnstore index | Microsoft Connect.
Put simply there is inconsistent behaviour when returning the data on a table that is stored using a Clustered Columnstore Index and a table that is not. There is also an issue when using the “Include Actual Execution Plan” from Managment Studio.
The item has two attachments that provide complete examples of the inconsistent behaviour. I have downloaded and have been able to reproduce on SQL Server 2014 CU3. If anyone else has SQL Server 2014 installed (needs to be Enterprise or Developer as partitioning is used) it’d be helpful if you can download and try to replicate.