Covering Indexes: Not Just for SELECT but also for UPDATE statements
Covering indexes help UPDATE performance also
2018-05-15
12,586 reads
Covering indexes help UPDATE performance also
2018-05-15
12,586 reads
2018-05-10
876 reads
Erik Darling shows how missing index requests have different impact numbers depending on the query's join type.
2018-04-26
7,058 reads
Erik purposely fragments indexes trying to slow down queries.
2018-02-15
3,508 reads
2018-02-06
1,000 reads
2018-06-07 (first published: 2018-01-13)
2,398 reads
2018-06-15 (first published: 2018-01-04)
2,122 reads
2017-11-02
1,049 reads
Erik Darling shows that if you take SQL Server's word when it asks for an index, things can go horribly awry.
2017-10-09
4,023 reads
2017-04-20
1,263 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