Columnstore index in sql server (tutorial)

[@dnfvideo]

20+ SQL Server Interview Questions : kzbin.info/www/bejne/iXbHcnluorh-iZY 30 Important C# Interview Questions : kzbin.info/www/bejne/eHzcn3h4hdacf68 25 Important ASP.NET Interview Questions : kzbin.info/www/bejne/ponQfpejf7p2Zsk 25 Angular Interview Questions : kzbin.info/www/bejne/Y5vIoKx6f6mmia8 5 MSBI Interview Questions : kzbin.info/www/bejne/a3abYmiXjaaqj7M

[@sumantabasu4450]

Really good overview of the concept. However one question - even for an OLAP scenario, if the requirement is to retrieve all the columns of a table by a select query on basis of an ID field , does column store index on each field really provides any benefit ? or just non clustered index on that id field is sufficient?

[@irfankhanmohammed6964]

Great explanation Sir. I have a question. Is Nonclustered columnstore index is different to nonclustered index? Can you please answer this? I am bit confuse.

[@rakeshranjan7647]

Yes it is , non cluster index store data row wise i e all column in a single page of 8 kb but when you create non clustered columnstore index on any column or group of column then each column is store in a separate 8 kb page

[@nikhilreddy8550]

If it is a Clustered Index, shouldn't the leaf node contain the actual entire row rather than pointing to the row? That is also the reason we can only have 1Clustered Index.

[@srinivasavula7268]

As a developer of ms sql server in my regular performance tuning I am creating indexes on queries having date columns as filters(ex retrieving the data created between 01-jan-2020 and 31-jan-2020),but sql server not recommended this column while creating the index...please explain...Thank you.

[@srinivasavula7268]

Nice explanation sir..Column store index will increase the overall table size right...

[@amitbhattacharyya5925]

Can it support around 600 million rows 90 col table where i would do col index on about 60 col ? Any idea

[@mohanpara4535]

how compression works ? Will it merge duplicate values in a column as a single value ?

[@BornDude25]

Yes,it applies compression on similar values which makes it more performant

[@好好好-y3b]

Thank you for the excellent explanation.

[@tejaswil1656]

Thank you sooooooooooooooooo much sir.... very clearly explained. This helps a lot💗🤝God bless you

[@pratikfutane8131]

Great explanation!

[@sridharramalingam329]

Very well explained, thanks

[@amitthorat6183]

Thank you! Highly engaging and informative video.

[@rekhakalyani2903]

Why am I not able to see clustered index in execution plan ? I have clustered and non clustered indexed on my table..when I click on execution plan I can't see the index just like your screen

[@thearchibaldtuttle]

Thank you for this intro!

[@baskarlakshmi889]

I have created columnstored index after that am faced error update statement failed because in a table that has a noncluster index. Consider disabling the volume tire index before issuing the update statement and then rebuilding the columstore index..Pls advice

[@sanjayschopra5316]

I need your help please let me know can we connect

[@dhanarajumattaparthi6399]

Nicely explained...

[@jatindersingh2241]

Very well explained , Thanks for sharing

[@vikaspandey4128]

Really nice article and it helps me in clearing my doubts.

[@theislamicvoyager]

I really like the explanation

[@avulasaikumar3081]

Thank you very much for this video.

[@TheOntheskies]

Very good explanation. Thank you!

[@ranjithashetty5773]

Can you please provide the link for step by step SQL videos

[@dnfvideo]

Here is the one hour video link for SQL step by step learning - kzbin.info/www/bejne/q3jPl4NvpJyeo7s

[@abraceyiii]

awesome explaination...keep up the good work

[@tushibhaque863]

Thanks fr this great tutorial...was waiting fr a video about columnstore index..

[@alexanderlinders4999]

Very helpful video!

[@kirankumarkommalapudi9947]

Column store index will have clusterd and non clusterd again? Syntax above creating non clusterd column store index...

[@ryanshannon7703]

A clustered column store index is ALL columns being column store, which probably won't make much sense in most scenarios. Even in a Fact table of an OLAP, I'm not sure how a clustered column store index would be beneficial, other than just not creating a bunch of nonclustered column store indices in terms of coding. Starting in SQL Server 2016, they allow non clustered index on column store (and vice versa), as when you start drilling down to very specific entries into your OLAP data, the non clustered index will be more helpful than the column store, which makes sense (less entries per page, but more relevant towards specific entries required for data return which means less densely packed pages to sift through). That's why for aggregates, column stores are like, way awesome.

[@koushikdey100]

Great 👌👌

[@ajaysharma2061]

Very much informative and helpful. Thank you for this.

[@arunkamble2008]

Excellent.

[@lkchannel1550]

Thanks.

[@georgetuccio6053]

Another amazing video. You guys are awesome.

[@nitikrish77]

superb...

[@krunalshah351]

great. example is very nice.

[@hemanttoday]

Great work

[@michauJi]

Great video :) Very benefitial.

[@angelamessina7187]

Thank you

[@prokhorov_sergey_igorevich]

Cool! Nice boost :)