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
96 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
96 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
46 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)
388 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)
595 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
147 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
137 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,947 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)
609 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
258 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)
550 reads
By Brian Kelley
I will be leading an in-person Certified Information Systems Auditor (CISA) exam prep class...
EightKB is back again for 2026! The biggest online SQL Server internals conference is...
By HeyMo0sh
Working in DevOps long enough teaches you two universal truths: That’s exactly why I...
Hi all, I just started using VS Code to work with DB projects. I...
Comments posted to this topic are about the item Fun with JSON II
Comments posted to this topic are about the item Changing Data Types
I have some data in a table:
CREATE TABLE #test_data
(
id INT PRIMARY KEY,
name VARCHAR(100),
birth_date DATE
);
-- Step 2: Insert rows
INSERT INTO #test_data
VALUES
(1, 'Olivia', '2025-01-05'),
(2, 'Emma', '2025-03-02'),
(3, 'Liam', '2025-11-15'),
(4, 'Noah', '2025-12-22');
If I run this query, how many rows are returned?
SELECT t1.[key] AS row,
t2.*
FROM OPENJSON(
(
SELECT t.* FROM #test_data AS t FOR JSON PATH
)
) t1
CROSS APPLY OPENJSON(t1.value) t2; See possible answers