A Problem with Cowboy Coding
Cowboy coding can be a problem, and in a case Steve talks about, a temptation for someone to get more work.
2020-01-08
513 reads
Cowboy coding can be a problem, and in a case Steve talks about, a temptation for someone to get more work.
2020-01-08
513 reads
2020-01-08
591 reads
Another post for me that is simple and hopefully serves as an example for people trying to get blogging as #SQLNewBloggers. When you install Windows, by default, the execution...
2020-01-08
145 reads
2020-01-07
684 reads
Steve thinks one of the ways you can stand out with your resume or CV is by writing well and attracting the attention of hiring managers.
2020-01-07
176 reads
I discovered recently that there was a change made in SQL Server 2017 to the way that symmetric key passphrases are hashed. There’s a KB article that notes the...
2020-01-06 (first published: 2019-12-23)
404 reads
2020-01-06
1,070 reads
Steve reminds you to be careful of taking shortcuts, as these can compromise security. Automation and DevOps might help you avoid mistakes.
2020-01-06
286 reads
This week Steve talks about the ways in which comments are important in our code.
2020-01-04
289 reads
2020-01-03
810 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