You’re responsible for the care and feeding of production SQL Servers, including index maintenance.
For years, you’ve heard that you’re supposed to reorganize your indexes to make SQL Server go faster. It sounds like it makes sense – keep things in order, right? But you keep doing it, and SQL Server isn’t getting any faster. You’ve even heard that setting fill factor will help prevent fragmentation, and you’re doing that too – but your indexes still keep getting fragmented every day, and users aren’t happy with performance.
This advice made a lot of sense at the turn of the century, but today, things are different – and we’re not just talking solid state drives. In just the first 15 minutes, you’ll have a series of ah-ha moments when you realize that your daily index maintenance jobs might just be making the problem worse instead of better. Then, you’ll learn what you need to do instead.
Why I Want to Present This Session:
The cool thing about the SQL Server community is that there’s over a decade of blog posts, presentations, and videos out on the net. The bad thing is that a lot of that is outdated, and now we have to combat that now-bad advice. I want to put something out there to make it clear why those nightly windows might be better spent checking for corruption instead of shuffling pages.
Latest posts by Brent Ozar (see all)
- How to Write a Good Abstract for GroupBy.org - May 4, 2017
- [Video] GroupBy Intermission: Brent, Erik, and Tara Take Questions - May 4, 2017
- #GroupBy June 2017 Lineup Announced, Registration Open - May 3, 2017