January 3, 2018 at 8:35 pm
Comments posted to this topic are about the item Columnstore Indexes on SQL Server 2016
January 3, 2018 at 8:38 pm
Good question, thanks Evgeny.
...
January 3, 2018 at 11:44 pm
Good question, Evgeny, thanks
Learned something new today
____________________________________________
Space, the final frontier? not any more...
All limits henceforth are self-imposed.
“libera tute vulgaris ex”
January 4, 2018 at 2:02 am
only one column store index is allowed each table then what the difference between clustered and column store index? :exclamationmark::exclamationmark::exclamationmark:
Manik
You cannot get to the top by sitting on your bottom.
January 4, 2018 at 2:41 am
---
January 4, 2018 at 7:19 am
manik_anu - Thursday, January 4, 2018 2:02 AMonly one column store index is allowed each table then what the difference between clustered and column store index? :exclamationmark::exclamationmark::exclamationmark:
In short:
A Clustered Columstore Index moves all of the existing data into the columnstore and removes the rowstore. Queries will be processed against the columnstore.
A Non-Clustered Columnstore Index copies the data into a columnstore and retains the existing rowstore. Depending on the query, it may be processed against the columnstore or the rowstore.
There are other differences, such as updatability and data type restrictions, but many of those depend on your SQL Server version.
For an overview, check Microsoft's documentation: https://docs.microsoft.com/en-us/sql/relational-databases/indexes/columnstore-indexes-overview
For a deep dive, I recommend Niko Neugebauer's extensive blog on the topic: http://www.nikoport.com/columnstore/
January 9, 2018 at 10:36 am
Great question. Thanks
Thanks.
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply