A New Word: Dead Reckoning
dead reckoning– v. intr. finding yourself bothered by somebody’s death more than you would have expected, even if they were only an abstract presence in your life, like a...
2025-11-21
13 reads
dead reckoning– v. intr. finding yourself bothered by somebody’s death more than you would have expected, even if they were only an abstract presence in your life, like a...
2025-11-21
13 reads
2025-11-21
152 reads
2025-11-21
742 reads
I wrote a piece on the new SUBSTRING in SQL Server 2025 and got asked a question. How do we get the last last name, such as only getting...
2025-11-19
144 reads
2025-11-19
590 reads
If you aren’t watching the Ignite keynotes today, then you might have missed the announcement that SQL Server 2025 officially releases today. The main SQL Server page gives you...
2025-11-18
47 reads
Last week I asked you to write about SQL Server 2025 and what things you might be looking forward to in the new version. First, as usual, is Rob...
2025-11-18
137 reads
AI can help us do more, but do we need to do more? Or more importantly, are we doing a good job of producing more useful stuff?
2025-11-17
188 reads
2025-11-17
648 reads
2025-11-15
99 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