2026-08-19
1,341 reads
Indexing
SQL Server index tuning: common mistakes and how to fix them
This guide walks through the most common SQL Server index tuning mistakes seen in production environments, such as over-indexing, oversized INCLUDE lists, unnecessary fill factor settings, misuse of SORT_IN_TEMPDB, over-aggressive index maintenance – and the myth that heaps are a shortcut to speed. Features real examples.
2026-08-17
Confession Time: I Never Taught You About B-Trees.
I work with databases for a living. I teach people, and I help them via consulting. And as far as I can remember, I’ve never written something about how b-trees work.
2026-07-15
Why Your Index Isn't Being Used? - Reading Execution Plans to Find the Real Culprit
Built the index, but SQL Server still scans the whole table? Learn how to read execution plans and find exactly why your index is being ignored.
2026-05-18
3,246 reads
Why use a Composite Index in SQL Server
SQL queries can take a long time to run, especially on large tables if not properly indexed. Full table scans can be costly operations when all a user wants is to fetch a few rows based on multiple columns and a WHERE filter. How can we properly index our tables to support multi-column queries?
2026-04-08
2025-12-15
1,404 reads
Managing Underused Indexes in SQL Server Availability Groups – Part 2
Knowing the usage from all workloads is definitely better than focusing on only the primary or a single secondary. But what if I want to make more informed decisions, incorporating row counts, size, and index columns into this output?
2025-10-27
Why Indexes are Important Beyond Faster Execution of Queries
Learn how indexes can help you with more than just querying data.
2025-10-22
18,443 reads
2025-06-23
478 reads
Index Scans and Table Scans
There are several things that you can do to improve performance by throwing more hardware at the problem, but usually the place you get the most benefit from is when you tune your queries. One common problem that exists is the lack of indexes or incorrect indexes and therefore SQL Server has to process more data to find the records that meet the queries criteria. These issues are known as Index Scans and Table Scans.
2025-06-06
Blogs
T-SQL Tuesday #203: Risk and Reward
By Steve Jones
This is timely, as I’m currently on a boat in the Adriatic taking a...
dataMinds Connect 2026 – Slides & Scripts
You can find the slides and SQL scripts for my session “Spice up your...
How to Clear the SSMS Cache (SSMS 21 and Later)
By SQLPals
How to Clear the SSMS Cache (SSMS 21 and Later) Updated...
Forums
Using CHOOSE()
Comments posted to this topic are about the item Using CHOOSE()
Re-Seeding a Broken Log Shipping Secondary (Without Touching the Primary)
Comments posted to this topic are about the item Re-Seeding a Broken Log Shipping...
The DBA is Dead! Long Live the !
Comments posted to this topic are about the item The DBA is Dead! Long...
Question of the Day
Using CHOOSE()
We have this code that sets some status values and then queries them using the CHOOSE() function in SQL Server 2025.
CREATE TABLE Status
(
StatusID INT,
StatusDescription VARCHAR(20)
);
GO
INSERT dbo.Status
(
StatusID,
StatusDescription
)
VALUES
(0, 'Uncategorized'),
(1, 'Active'),
(2, 'Inactive'),
(3, 'Temp');
GO
SELECT CHOOSE(StatusID, 'Unknown', 'Active', 'Inactive', 'Temporary')
FROM Status;
When the SELECT runs, what is returned? See possible answers