2023-04-07
347 reads
2023-04-07
347 reads
An extra column in an information_schema view had Steve digging into standards.
2023-04-05
174 reads
2023-04-05
561 reads
There is a survey from the WIT group for female speakers. If you are a woman and speak in front of groups, or used to, please fill it out....
2023-04-05
42 reads
2023-04-03
557 reads
The grade for March is also D. Details below, but just not making a lot of progress in these areas. In fact, I find myself not motivated to work...
2023-04-03
15 reads
Steve has to use software that is broken, but it's OK. It actually works well enough.
2023-04-03
117 reads
This week Steve found a question of whether SQL Server 2019 uses more CPU than 2016.
2023-04-01
719 reads
Steve thinks building a brand is important in today's competitive world of job seekers.
2023-03-31
125 reads
2023-03-31
347 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