SQLServerCentral Editorial

How can we standardize SQL Server Data Deployments?

Some change requests, such as deploying a new stored procedure or trigger, are relatively easy to manage whereas others, such as data deployments, tend to thwart all attempts at standardization. And yet, there must be a way, and Rodney Landrum believes that DBA-developer co-operation lies at the heart of it.

(2)

You rated this post out of 5. Change rating

2009-12-16

300 reads

SQLServerCentral Editorial

Had this been an actual emergency….

Rodney Landrum has lived through several simulated emergencies and one real one, in the form of Hurricane Ivan. The tests do not adequately prepare you for the real thing. Real emergencies bring tension, exhaustion and hunger pangs. Simulations bring lethargy, pre-determined end times, and warm pizza.

(1)

You rated this post out of 5. Change rating

2009-09-07

179 reads

Blogs

In-Person CISA Training – April 13-16, 2026

By

I will be leading an in-person Certified Information Systems Auditor (CISA) exam prep class...

EightKB 2026

By

EightKB is back again for 2026! The biggest online SQL Server internals conference is...

The FinOps Lifecycle: From Budgeting to Reporting

By

Working in DevOps long enough teaches you two universal truths: That’s exactly why I...

Read the latest Blogs

Forums

VS Code, Unresolved References.

By mjdemaris

Hi all, I just started using VS Code to work with DB projects.  I...

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

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