In many environments, it’s useful to know exactly when an index was created or modified.
Did that last code release help performance, or hurt it? It’s really helpful to know exactly when the code was deployed to prove that your change made something better. Or that you might need to roll it back.
It takes a little preparation to track changes to your indexes, but it’s easy to implement.
Short answer: the SQL Server optimizer will know that the table was truncated, but statistics might not update when you expect.
For the long answer, let’s walk through an example using the WideWorldImporters sample database.
Whether I’m working as a DBA, a consultant, a teacher, or just answering questions in my inbox, I always end up needing a script to inspect statistics one way or another.
Here are some freshly written scripts for a classic DBA question: what’s going on in my stats?
Does your team know what it’s doing with SQL Server?
Learn what a consultant looks for when assessing a team, and signs that SQL Server may be badly configured.
Want to learn to tune indexes in SQL Server? I’ll be teaching a day-long pre-conference session in Portugal in March. Hope to see you there, or at SQL Saturday Lisbon (free!) the following weekend.
You’ve got an important stored procedure that you think needs index help– but it runs in environment with lots of other queries. How do you focus in and discover exactly what indexes need tuning for that procedure?
Today’s question is about why a query might be slow at first, then fast the next time you run it.
Copyright (c) 2025, Catalyze SQL, LLC; all rights reserved. Opinions expressed on this site are solely those of Kendra Little of Catalyze SQL, LLC. Content policy: Short excerpts of blog posts (3 sentences) may be republished, but longer excerpts and artwork cannot be shared without explicit permission.