2006-07-28
1,959 reads
2006-07-28
1,959 reads
2006-07-27
1,281 reads
2006-07-26
1,683 reads
2006-07-25
1,076 reads
2006-07-24
1,304 reads
2006-07-21
1,095 reads
Stored procedures are a great way to encapsulate code and reuse it in many places in your application. But when you have a performance issue, how do you know which part of the stored procedure is giving you problems? Steve Jones takes a look at a few techniques for diving into stored procedures and identifying problem areas.
2006-07-20
28,830 reads
2006-07-20
1,508 reads
2006-07-19
1,014 reads
2006-07-18
1,499 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