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.
I got a great question about Edition downgrades recently.
SQL Server has two types of filtered indexes:
If you use SQL Server’s blocked process report or collect deadlock graphs, occasionally you’ll come across things that look like this:
waitresource=“PAGE: 6:3:70133 " waitresource=“KEY: 6:72057594041991168 (ce52f92a058c)”
I get a lot of requests about which books are helpful to learn performance tuning and database design. I totally get that – I still like learning with books. It doesn’t mean training videos or blogs are any less cool. They can all work together.
Should you look at automatically created statistics on your tables in SQL Server to help you design better indexes? Learn why in this 20 minute video, or subscribe to the Dear SQL DBA podcast.
No time to watch? Scroll on down, everything is written in article form below the video.
Here’s this week’s question:
If you haven’t checked out Microsoft’s new WideWorldImporters sample database for 2016, it’s a pretty cool new little database. The database makes it easy to play around with new 2016 features, and it even ships with some cool little executables to run inserts in the “workload-drivers” folder.
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.