SQLServerCentral Editorial

You Never Know

I'm writing this sitting at the PASS Data Community Summit. It's been a fantastic event. I gave a community session on Azure DevOps. I was able to help Redgate launch a new product. I've received a bunch of hugs from VERY dear old friends. I've met a ton of people. It's been great. Allow me […]

SQLServerCentral Article

Scheduling SQL Agent Jobs on Alternating Weeks

Bi-week... semi-week... fortnight... "every two weeks" Recently on the SQL Community Slack group, someone asked if there was a way to schedule a backup to run on alternate weeks. I'm not exactly sure why (maybe they wanted to run full and differential backups on alternating weeks), but yes, we can do that. In part one […]

Blogs

Finding and Updating Duplicate IDs: #SQLNewBlogger

By

Finding duplicates was an interview question for me years ago, and I’ve never forgotten...

Optimising Costs: Strategies for Efficient Cloud Resource Management

By

Over time, I’ve realised that one of the hardest parts of cloud management isn’t...

Cost Visibility: Tracking and Analysing Your Cloud Spend

By

One of the biggest challenges I’ve faced in cloud operations is maintaining clear visibility...

Read the latest Blogs

Forums

Fun with JSON II

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Fun with JSON II

Changing Data Types

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Changing Data Types

Answering Questions On Dropped Columns

By Cláudio Silva

Comments posted to this topic are about the item Answering Questions On Dropped Columns

Visit the forum

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