Columnstore Indexes: What are waiting for? by Niko Neugebauer

GroupBy – Free SQL Server Training

Content provided by Brent Ozar. All podcast content including episodes, graphics, and podcast descriptions are uploaded and provided directly by Brent Ozar or their podcast platform partner. If you believe someone is using your copyrighted work without your permission, you can follow the process outlined here https://player.fm/legal.

5y ago 1:18:35

MP3•Episode home

Archived series ("Inactive feed" status)

When? This feed was archived on January 29, 2020 15:10 (4y ago). Last successful fetch was on October 18, 2019 15:18 (4+ y ago)

Why? Inactive feed status. Our servers were unable to retrieve a valid podcast feed for a sustained period.

What now? You might be able to find a more up-to-date version using the search function. This series will no longer be checked for updates. If you believe this to be in error, please check if the publisher's feed link below is valid and contact support to request the feed be restored or if you have any other concerns about this.

Every time you see a Columnstore Index getting involved in the execution plan, do you realize that there are whole execution plans behind those Index Scans ? Did you ever ask yourself, what are those strange and weird HT_* waits stand for ? Why do we wait for seconds/minutes for something like HTBUILD while it seems that nothing happens ? Why do we have a ROWGROUP_VERSION wait on one server, while the other allows queries to run faster ?

This session focuses on answering those question - to help you understand the reasons and the conditions behind every single available wait for the Columnstore Indexes and the Batch Execution Mode.

74 episodes

#Prog Languages #Science #Database #Sqlserver #Training #Brent Ozar #Tech #Podcasting Education #Communities #Development