Emergency Preparedness
Being prepared for things to go wrong is important, more so these days than in much of our past.
2020-09-04
91 reads
Being prepared for things to go wrong is important, more so these days than in much of our past.
2020-09-04
91 reads
This week Grant notes that we need to work on our learning skills, especially as the world continues to drive forward.
2020-08-29
203 reads
2020-08-01
116 reads
Today Grant talks about the challenges of sometimes finding good, current information.
2020-06-15
127 reads
2020-05-09
144 reads
2020-04-11
133 reads
2020-02-20
334 reads
2020-02-17
175 reads
2020-02-13
216 reads
Because of my job with Redgate (which I love and will never leave even after I’m dead), I spend a lot of time learning about compliance and all the new laws and regulations coming out of things like the GDPR and the CCPA (they changed the name evidently). However, I’m a nerd. I’m not a […]
2020-02-08
148 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...
Hi all, I just started using VS Code to work with DB projects. 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
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