Columnstore indexes are especially useful for DataWarehousing (DW) . This means that you will only be updating or uninstalling at a specific time.
This is due to their special design with delta loading and a large number of functions. This video will demonstrate great detail and a good basic overview of what the exact difference of the Columnstore Index is .
Traditional
If you have high input / output (input and output) of the application; Columnstore index is not perfect, as traditional row indexing will find and manipulate (using strings found through the index) for this particular purpose. An example of this is an ATM application, which often changes the values โโof account data strings .
Columnstore
Indexing column indices throughout COLUMNS , which is not ideal in this case, since row values โโwill be distributed in segments (columnsindexes).
I highly recommend the video!
I also want to dwell on the cluster cluster storage of clusters:
The non-clustered Columnstore (update in 2012) saves WHOLE data again, which means (2X data) twice the data.
Where as a cluster column index (update in 2014) only 5 MB is required for approximately 16 GB of data. This is due to RTE (run-time coding), which stores the amount of duplicate data in each column. Creating an index takes up less space.
source share