Your SQL Server Is Whispering…Are You Listening?
Early Warnings of a Meltdown (and How to Catch Them) Most SQL Server crashes don’t come out of nowhere. They leave breadcrumbs – red flags that something’s not right....
2025-05-07
116 reads
Early Warnings of a Meltdown (and How to Catch Them) Most SQL Server crashes don’t come out of nowhere. They leave breadcrumbs – red flags that something’s not right....
2025-05-07
116 reads
Ever tried to request SQL Server funding from the CFO? Your systems, your data, your customer experience – they all rely on that “invisible” database engine humming along behind...
2025-05-01
70 reads
Everything in SQL Server is waiting for something…this is by design. And most people never think about it… Until your application is waiting to complete its request, sell the...
2025-04-30 (first published: 2025-04-16)
414 reads
Does skipping a DBA save money? Wait until your system grinds to a halt, your backups fail, or your cloud bill skyrockets. The “DBA? We Don’t Need No Stinkin’...
2025-04-14 (first published: 2025-04-02)
608 reads
SQL Server backups are database insurance – you don’t really appreciate them until disaster strikes. But here’s the kicker: having backups doesn’t mean your data is safe. If you’re...
2025-04-09
162 reads
The Source Control Dilemma Every DBA has been there. Trying to keep track of database schema changes while developers have their fancy Git repositories and version control workflows. Meanwhile,...
2025-03-27
155 reads
IT leaders have a lot on their plates! Budgets, staffing, security, uptime, and keeping everything running smoothly. When SQL Server performance becomes an issue, a common reaction is often...
2025-03-26 (first published: 2025-03-13)
6,962 reads
We get it. There’s no budget for a DBA on staff, or even a contract support firm like Dallas DBAs. You are not alone! There are thousands of firms...
2025-03-19 (first published: 2025-03-07)
625 reads
Don’t Panic! It’s a vague but common complaint, frequently with no additional details. Before blindly restarting SQL Server, let’s walk through quick checks that don’t require deep DBA skills....
2025-03-19
281 reads
Common Reasons for Emergency SQL calls If you are a production DBA (or Accidental prod DBA) you’ve gotten that frantic call in the middle of the night. Or maybe...
2025-03-12 (first published: 2025-02-28)
570 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