2005-08-09
1,508 reads
2005-08-09
1,508 reads
the more I'm sure that I'm getting dumber with SQL Server.
This week I've been working on some QODs based...
2005-08-09
1,356 reads
I scan about 30 or 40 blogs these days, all from various SQL Server
people around the globe, and enter the...
2005-08-08
1,454 reads
I got asked by someone to technically review their SQL Server 2005
book, so I'm betting that there will be lots...
2005-08-05
1,452 reads
2005-08-05
2,705 reads
Why should a SQL Server DBA want to keep their job? It seems obvious, but Steve Jones continues with his series on employee retention by taking a look at it from the employee side.
2005-08-04
10,508 reads
2005-08-03
2,034 reads
2005-08-02
2,090 reads
Interesting post by Andy Leonard.
I'll add in my two cents that you should seek happiness and
satisfaction in your job. I...
2005-07-29
1,519 reads
2005-07-29
1,784 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