SQL Server Columnstore Index question concept

techresearch7777777 1,801 Reputation points

Hello, trying to understand the concept of Columnstore Index vs typical standard regular index and came across this interesting post:


To simplify the concept (realize there's further technical portions involved) could Columnstore Index be viewed as transposing the typical standard index the way they store entire row on per page...instead of horizontal (typical standard) they are stored vertically (Columnstore) like the article mentions it then it would only need to read 1 page only rather than multiple rows in their example?

Thanks in advance.

SQL Server
SQL Server
A family of Microsoft relational database management and analysis systems for e-commerce, line-of-business, and data warehousing solutions.
13,277 questions
0 comments No comments
{count} votes

2 answers

Sort by: Most helpful
  1. Erland Sommarskog 106K Reputation points MVP

    In a columnstore data is stored columnwise, rather than rowwise. It is not really an index in the sense that it is sorted. To find a specific row where City = 'Horbart', you would need to scan all rows, but only for that column. And since all occurrences of Horbart can be stored in once place, there are fantastic options for compression.

    The article you linked to, see to have many good links, and if you google, you can find even more. It's not clear what you expect us to explain here, that you cannot find on the internet already.

    0 comments No comments

  2. LiHongMSFT-4306 25,571 Reputation points

    Hi @techresearch7777777

    Referring to this doc: Columnstore indexes: Overview

    Rowstore indexes perform best on queries that seek into the data, when searching for a particular value, or for queries on a small range of values. Use rowstore indexes with transactional workloads because they tend to require mostly table seeks instead of table scans.

    Columnstore indexes give high performance gains for analytic queries that scan large amounts of data, especially on large tables. Use columnstore indexes on data warehousing and analytics workloads, especially on fact tables, because they tend to require full table scans rather than table seeks.

    Also, you can combine rowstore and columnstore on the same table. Beginning with SQL Server 2016 (13.x), you can have one or more nonclustered rowstore indexes on a columnstore index and perform efficient table seeks on the underlying columnstore.

    Best regards,

    Cosmog Hong

    If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

    Note: Please follow the steps in our Documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    0 comments No comments