2019-09-17
1,113 reads
Indexing
How much will it cost or save to rebuild that index? (SQL Oolie)
What's the true and permanent cost of lowering the Fill Factor of an index in SQL Server? It's a lot more than many people think. 9 year SQL Server MVP veteran, Jeff Moden, demonstrates how to calculate the extra space that will be used by lowering the Fill Factor and saved by increasing it.
2021-05-28 (first published: 2019-09-03)
10,463 reads
A Self-Tuning Fill Factor Technique for SQL Server – Part 2
Introduction Fill Factor is a parameter most of us have ignored because there is no definitive way to calculate what the correct value should be. Part 1 of this series describes a new technique to dynamically determine index fill factors for all indexes within a database. Part 2 covers an analysis of the data collection […]
2019-08-27
4,024 reads
Some T-SQL INSERTs DO Follow the Fill Factor! (SQL Oolie)
With origins from the world of “Submarine ‘Dolphin’ Qualification” questions, an “Oolie” is a difficult question to answer, or the knowledge or fact needed to answer such a question, that may or may not pertain to one's duties but tests one's knowledge of a system or process to the limit. Introduction Contrary to what many […]
2019-08-08
6,474 reads
More On Column Order Indexes – Part 2
Continued analysis of index architecture with revised clustered index. Part 2 of Column Order Indexes
2020-12-11 (first published: 2019-04-24)
2,649 reads
What happens when you cancel or kill a resumable index creation?
SQL Server 2019 adds resumable online index creation, and it’s pretty spiffy according to Brent.
2019-04-11
Are nulls stored in a nonclustered index?
When you index a nullable field, are the rows with nulls stored in the index? It’s easy enough to find out by creating a table with a nullable field, and then creating an index on it.
2019-03-29
2019-03-28
419 reads
Can deleting rows make a table…bigger?
Michael J. Swart posted an interesting question: he had a large table with 7.5 billion rows and 5 indexes. When he deleted 10 million rows, he noticed that the indexes were getting larger, not smaller.
2019-03-22
2,752 reads
2018-11-09
824 reads
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