2007-08-14
1,442 reads
2007-08-14
1,442 reads
2007-08-13
2,577 reads
There has been tons of work over the last few decades on queueing theory, mainly in regard to operating systems...
2007-08-11
1,675 reads
2007-08-10
1,636 reads
I got a note from someone at Red Gate about disengagement with the newsletter and site. Actually it was my...
2007-08-09
1,410 reads
2007-08-09
1,638 reads
It's not directly SQL Server, but it does prevent me from working with SQL Server 🙂
So I'm in Virginia this...
2007-08-08
2,899 reads
2007-08-08
1,604 reads
Maybe not. This is a great post and cartoon from David Reed (a friend) mentioning me.
We've had some good arguements...
2007-08-07
1,587 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
By HeyMo0sh
Over time, I’ve realised that one of the hardest parts of cloud management isn’t...
By HeyMo0sh
One of the biggest challenges I’ve faced in cloud operations is maintaining clear visibility...
By Steve Jones
I come to Heathrow often. Today is likely somewhere close to 60 trips to...
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