TSQL Tuesday #2
I’ve wracked my brain for some bit of puzzle that I could present as part of TSQL Tuesday #2 and I...
2010-01-12
1,121 reads
I’ve wracked my brain for some bit of puzzle that I could present as part of TSQL Tuesday #2 and I...
2010-01-12
1,121 reads
You must read this post from Tim Ford to understand why I might do this on my technical blog. But...
2010-01-11
883 reads
The second annual New England Data Camp is shaping up to one excellent event. We’ve put together a great set...
2010-01-11
550 reads
The big day has arrived and all the speakers are poring over their PASS Summit 2009 evaluations, me included. These...
2010-01-06
694 reads
Today we have a guest editorial from Grant Fritchey. The Boy Scouts motto is "be prepared" and most of you probably unconsciously follow that in your daily lives. Why is it that so many of us don't follow through on this same advice with our databases? Grant Fritchey gives a few examples of how you should "be prepared" for a database emergency.
2010-01-04
376 reads
I’d really like to publish your article in SQL Server Standard. All I need from you is an abstract, a...
2010-01-04
959 reads
Today we have a guest editorial from Grant Fritchey. The Boy Scouts motto is "be prepared" and most of you probably unconsciously follow that in your daily lives. Why is it that so many of us don't follow through on this same advice with our databases? Grant Fritchey gives a few examples of how you should "be prepared" for a database emergency.
2010-01-04
2,109 reads
Today we have a guest editorial from Grant Fritchey. The Boy Scouts motto is "be prepared" and most of you probably unconsciously follow that in your daily lives. Why is it that so many of us don't follow through on this same advice with our databases? Grant Fritchey gives a few examples of how you should "be prepared" for a database emergency.
2010-01-04
2,707 reads
Today we have a guest editorial from Grant Fritchey. The Boy Scouts motto is "be prepared" and most of you probably unconsciously follow that in your daily lives. Why is it that so many of us don't follow through on this same advice with our databases? Grant Fritchey gives a few examples of how you should "be prepared" for a database emergency.
2010-01-04
2,236 reads
And really bad plagiarism at that.
I received an email from someone suggesting I check out a book on Lulu.com, that...
2010-01-01
1,029 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