Tech on Tap v1.1 Wrap-up
The first ever Tech on Tap event was held on Saturday, January 27th, 2012 at the Stone Cellar Brewpub in...
2012-01-31
2,071 reads
The first ever Tech on Tap event was held on Saturday, January 27th, 2012 at the Stone Cellar Brewpub in...
2012-01-31
2,071 reads
The question came up, what are the top 3-5 things that you look at in a query. I realized then...
2012-01-30
1,827 reads
There are four different ways you can get information about deadlocks in your system. These are:
traceflag 1204traceflag 1222trace eventsextended eventsFor...
2012-01-27 (first published: 2012-01-23)
3,082 reads
I’m not going to black out my blog, because, let’s face it, who’s going to notice? But for all six...
2012-01-18
1,920 reads
I want to say a few things about database backups that you need to know.
Wait a minute, haven’t you written...
2012-01-16 (first published: 2012-01-11)
5,164 reads
Gee thanks Jes (blog|twitter). Just what I wanted, a little extra work on a Friday afternoon. I used to like...
2012-01-13
1,435 reads
I say it all the time because it’s worth repeating, feedback is a gift. Good, bad or indifferent (well, not...
2011-12-19
1,730 reads
I’ll be presenting at the Colorado Springs SQL Saturday on January 7th of 2012. The session is called Seven Ways...
2011-12-14
1,932 reads
I’ve been working with execution plans quite a lot in SQL Server 2012. There are a number of changes, most of them associated with new or different functionality. I had not noticed anything really fundamental until recently. I’ve become a huge proponent of always checking the properties of the SELECT statement. There’s so much useful information in there about what’s happened with the plan generation in the optimizer (not low level stuff, but the big picture items) that you should always be checking it first as a fundamental part of your plan examinations.
2011-12-14
6,689 reads
I’ve been working with execution plans quite a lot in SQL Server 2012. There are a number of changes, most...
2011-12-12
10,169 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