SQL Server Is Slow – Part 2 of 4(?)
The 10-Minute Outside-In Triage Don’t Blame SQL First It’s 9:05 AM and your helpdesk lights up: “The SQL Server is down. Nothing works.” By 9:07, everyone is staring at...
2025-09-24
36 reads
The 10-Minute Outside-In Triage Don’t Blame SQL First It’s 9:05 AM and your helpdesk lights up: “The SQL Server is down. Nothing works.” By 9:07, everyone is staring at...
2025-09-24
36 reads
Old Reliable Still Matters If you’ve been around SQL Server for a while, you’ve heard of Failover Cluster Instances (FCIs). They’ve been part of SQL’s high availability toolbox since...
2025-09-19 (first published: 2025-09-03)
231 reads
It’s not glamorous, but it works In a world where shiny new HA/DR features get all the press, there’s one SQL Server technology that just keeps doing its job....
2025-09-15 (first published: 2025-08-27)
238 reads
Flexibility and Scale at the Database Level When SQL Server 2012 introduced Availability Groups (AGs), they changed the HA/DR game. Unlike Failover Cluster Instances (FCIs), which protect the whole...
2025-09-10
37 reads
“SQL Server is slow.” We’ve all heard it. But that doesn’t always mean SQL Server is the problem. And “slow” means nothing without context and ability to verify. More...
2025-08-27 (first published: 2025-08-06)
525 reads
If you’re responsible for a SQL Server instance, you need working, consistent backups. Not just a .bak file here and there, but a plan that runs automatically and covers...
2025-08-20
57 reads
If you’re a DBA, sysadmin, IT manager, or Accidental DBA, you’ve probably seen SQL Server’s built-in Maintenance Plans. They live right there in SSMS under the “Management” node, quietly...
2025-08-15 (first published: 2025-07-30)
459 reads
Corruption isn’t a “maybe someday” problem – what you need to do now. Stop. Don’t panic. You just ran DBCC CHECKDB for the first time in a while (or...
2025-08-13
36 reads
The SQL Server installer has gotten better: tempdb configuration, MAXDOP, and even max memory can now be configured during setup. But don’t be fooled: there’s still a post-install checklist...
2025-07-23
82 reads
Why You Shouldn’t Overlook This Quiet but Critical SQL Server Setting If you’ve ever upgraded a SQL Server instance and something just broke in your application, chances are...
2025-07-16
474 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