Risky Behavior
An interesting debate from one of my editorials on risk. Some great points raised by everyone, but I still think...
2007-08-07
602 reads
An interesting debate from one of my editorials on risk. Some great points raised by everyone, but I still think...
2007-08-07
602 reads
2007-08-07
1,690 reads
2007-08-06
1,703 reads
We've dropped an acronym!
In my rounds of the blogs today, a number of people have pointed out that SQL Server...
2007-08-03
537 reads
2007-08-03
1,692 reads
2007-08-02
1,709 reads
I'm downloading now, and you need some sort of inviation to do so, but it's available and ready for you...
2007-08-01
612 reads
2007-08-01
1,671 reads
2007-07-31
1,737 reads
Steve Jones bimonthly car update looks at driving in the UK and the differences in cars between the US and elsewhere.
2007-07-30
38 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...
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
Comments posted to this topic are about the item Answering Questions On Dropped Columns
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