2026-03-16
771 reads
2026-03-16
771 reads
2026-03-09
919 reads
2026-03-04 (first published: 2026-03-02)
1,033 reads
2026-02-16
678 reads
Learn about the new ZSTD compression algorithm in SQL Server 2025.
2025-12-29
2,074 reads
Learn how backup and restore work in Azure SQL Hyperscale in this next level in the stairway series.
2025-12-17
791 reads
2025-10-27
1,176 reads
There are multiple reasons for no full backup: corrupted backups, taking too much time to restore, etc. In this post, I want to show an alternative for these cases, an ace up one’s sleeve, that you can use to recover data.
2025-06-23
Who among us hasn't deleted a production data file? Steve hopes most of us have not.
2025-05-30 (first published: 2025-05-12)
207 reads
2025-03-28
1,145 reads
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...
By Brian Kelley
If your organization is spending money, then meaningful results are a must. Pen testing...
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