At Redgate Software, we've been trialing Copilot from GitHub with our developers. I managed to get access for this experiment and have tried a few things, though I'm not sure I've found it very useful. I'll continue to work with Copilot, but for now, I just don't find Copilot AI helping me with the types […]
2023-07-31
209 reads
Reviewing Pull Requests (PR) is something that developers should take seriously, but Steve doesn't think this always happens.
2023-07-28
351 reads
An interesting approach to schema changes is a creative solution to Steve. He asks if you have other creative solutions you've seen.
2023-07-21
140 reads
Steve saw a policy on code usage in software development and wondered how many companies have this.
2023-07-19
164 reads
Today Steve talks APIs, which are important in much of software development. He thinks we ought to treat our database schema as part of an API.
2023-05-22
283 reads
2023-05-10
175 reads
2023-05-08
188 reads
2023-05-01
135 reads
Who should create documentation for software? In many companies, it's the developers. In fact, in Redgate, often our developers are tasked with updating articles for products on our documentation site. We do have a streamlined process that has developers can submitting changes in some format (markdown? ) and an automation process that automatically updates the […]
2023-04-26
221 reads
Someone makes a case for using a Document DB rather than a RDBMS. Steve has a few thoughts.
2023-04-24
173 reads
By Steve Jones
Finding duplicates was an interview question for me years ago, and I’ve never forgotten...
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...
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