While preparing for my SQL Saturday Salt Lake City presentation, Climbing the B-Tree, I ran into one of the “word of mouth” facts that the first column of an index should be highly selective, i.e., it should only point to one or a few rows. This is not always the case and I’ll show you […]
2023-01-02 (first published: 2020-09-16)
5,680 reads
2020-07-10
598 reads
Today Kendra talks about two of the online options used when working with indexes.
2020-01-14
380 reads
2019-12-16
872 reads
2019-12-09
1,449 reads
2019-10-15
819 reads
Learn how the INCLUDE phrase of an index can change the performance of a query.
2019-10-10
28,933 reads
2019-10-08
743 reads
2019-10-01
1,000 reads
Learn about the advantages and disadvantages of using INCLUDE columns in your index.
2021-04-30 (first published: 2019-09-17)
29,535 reads
By Steve Jones
This is timely, as I’m currently on a boat in the Adriatic taking a...
You can find the slides and SQL scripts for my session “Spice up your...
By SQLPals
How to Clear the SSMS Cache (SSMS 21 and Later) Updated...
Comments posted to this topic are about the item Using CHOOSE()
Comments posted to this topic are about the item Re-Seeding a Broken Log Shipping...
Comments posted to this topic are about the item The DBA is Dead! Long...
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