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
24 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
24 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)
210 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)
217 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
23 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)
503 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
30 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)
426 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
23 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
69 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
455 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