Introductions and Overview
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