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.

Author: Richie Lee

Full time computer guy, part time runner. Full time Dad, part time blogger. Knows a thing or two about Pokémon. Knows too much about SQL Agent. Writer of fractured sentences. Maker of the best damn macaroni cheese you've ever tasted.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s