thanks for the video. However, sounds like you're creating an index to remove the sort operator. But, is it really worth the extra overhead of maintaining the extra index?
If we have more column in table and in UI we display that all column and user can sort any column from the UI so how to design index for that kind of scenario.
Agree. I’ll have to experiment on larger queries where you need a different index to seek, but if there are other columns to Order By, maybe a secondary index specifically on the sort column would get picked up to knock out both issues, similar to OR conditions using multiple indexes.
thanks for the video. However, sounds like you're creating an index to remove the sort operator. But, is it really worth the extra overhead of maintaining the extra index?
If we have more column in table and in UI we display that all column and user can sort any column from the UI so how to design index for that kind of scenario.
Amazing Video!
Agree. I’ll have to experiment on larger queries where you need a different index to seek, but if there are other columns to Order By, maybe a secondary index specifically on the sort column would get picked up to knock out both issues, similar to OR conditions using multiple indexes.
Thank you sir, wonderful technique 👏
Thanks for your valuable share. I have a question, is it necessity to order for include columns?
What's the impact on page reads and execution time?
Nice video sir.