Fundamentals of Columnstore Indexes Instant Replay
Your report queries are too slow.
You’ve tried throwing some hardware at it: your production SQL Server has 12 CPU cores or more, 128GB RAM, and SQL Server 2016 or newer. It’s still not enough to handle your growing data. It’s already up over 250GB, and they’re not letting you purge old data.
Will columnstore indexes help?
In one day, you’ll learn:
- How columnstore data is stored, and how that impacts your architecture choices
- How to do a hands-on self-assessment of your workloads, data, and server to figure out whether columnstore indexes make sense for you
- Why partitioning makes so much sense for columnstore indexes
- How to do a proof-of-concept implementation with initial creation, querying, ongoing loads, and index maintenance
Your Progress So Far in This Class
This is driven by the mark-as-complete buttons in each module of the class. (Let’s be honest: you’re probably just going to mark them as complete because you’re that kind of student. I feel you.)
- 0.1 Prerequisites Before the Class
- 0.2 How to Set Up Your Own Lab Server
- 01 How Columnstore Data is Stored
- 02 How Columnstore Data is Deleted, Updated, and Inserted
- 03 How Columnstore Data Is Selected
- 04 How Columnstore Data is Rebuilt
- 05 Clustered Columnstore Quiz: Is Your Table a Good Fit?
- 06 Nonclustered Columnstore Advantages
- 07 A Better Clustered Columnstore Candidate
- 08 Partitioning Is a Great Partner for Columnstore
- 09 Recap