When you modify the indexes on a table, SQL Server needs to reconsider how it executes queries that reference that table. But the way this appears when you’re looking at your execution plan cache is far from obvious: Impacted query plans are NOT removed from cache at the time you change an index. The next time the query is executed, it will be recompiled, and the new plan and related execution information will be placed in cache.
Some of the biggest lessons I’ve learned about interviewing come from an interview experience that meant a ton to me – and all my dreams came crashing down.
A user recently asked me what a good use case might be to run SQL Server on Linux in a Docker container.
Welcome to T-SQL Tuesday for August 2017!
T-SQL Tuesday is a chance for you to join in the SQL Server community and write a blog post on a suggested topic. You can use this as a way to start a new blog, dust off a blog you haven’t used in a while, or make it part of regular blogging: your choice!
I would love for you to participate. The whole SQL Server community would. Please, join us!
One cool little feature in SQL Server 2016 is COMPRESS(). It’s a TSQL function available in all editions that shrinks down data using the GZIP algorithm (documentation).
I’ve been having lots of fun drawing and doing webcasts this summer. I’ve got four SQL Server themed desktop wallpapers to share, and I’ve got lots more coming– along with a new chunk of free webcasts.
I’ve set things up so you can quickly download desktop wallpapers featuring cartoons and SQL Server concepts. Get ‘em here Grab wallpapers at https://github.com/LitKnd/littlekendracomments/tree/main/SQLWorkbooks-Wallpaper-and-Posters.
Table partitioning makes execution plans a bit more confusing. I have a free online course which walks you through decoding execution plans, including whether or not partition elimination occurred.
It can be tricky to remember that SQL Server doesn’t short circuit on IF statements in stored procedures. Even when you know this, sometimes it’s hard to recognize the impacts.
Working with maintenance plans is supposed to be easy, but I find it to be quite difficult.
Copyright (c) 2024, 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.
