2015-06-09
1,472 reads
Windows Azure
Microsoft Azure Diagnostics Part 1: Introduction
Having a well thought-out plan for diagnostic data is important for on-premises applications, but it is arguably more important for distributed, highly scalable cloud applications. Michael Collier has provided a clear introduction to Microsoft Azure Diagnostics, including the Diagnostics Agent and how to extract the data.
2014-05-16
2,747 reads
Automating the Retrieval of SQL Backups from Windows Azure BLOB Storage
If your database server is in Azure, then it makes sense to do backups into Azure too. SQL Server 2014 supports backups to the cloud, and particularly well with Managed Backup. Once your backups are safely in an Azure BLOB, then what? Mike Wood takes up the story.
2014-03-24
2,259 reads
Blogs
In-Person CISA Training – April 13-16, 2026
By Brian Kelley
I will be leading an in-person Certified Information Systems Auditor (CISA) exam prep class...
EightKB 2026
EightKB is back again for 2026! The biggest online SQL Server internals conference is...
The FinOps Lifecycle: From Budgeting to Reporting
By HeyMo0sh
Working in DevOps long enough teaches you two universal truths: That’s exactly why I...
Forums
Fun with JSON II
Comments posted to this topic are about the item Fun with JSON II
Changing Data Types
Comments posted to this topic are about the item Changing Data Types
Answering Questions On Dropped Columns
Comments posted to this topic are about the item Answering Questions On Dropped Columns
Question of the Day
Fun with JSON II
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