All the Costs of Downtime
Downtime causes a lot of problems, not all of which are financial for an organization.
2025-09-22
122 reads
Downtime causes a lot of problems, not all of which are financial for an organization.
2025-09-22
122 reads
A few recent disasters inspire Steve to remind you to prepare now, before a disaster occurs.
2024-08-02
112 reads
I’ve talked about it before; you shouldn’t have a backup strategy, you should have a recovery strategy.
2024-07-29
2024-04-03
681 reads
2024-03-21
491 reads
We are excited to share that there are several Accelerated Database Recovery enhancements in SQL Server 2022.
2023-12-01
An Azure datacenter had a failure after an incident, partially because they didn't have enough people. Steve notes that staffing is a challenge in many ways.
2023-09-29
171 reads
A disaster in LA affected many companies, some of which were innocent bystanders to the event. Steve talks about the need to have some plans in place.
2023-06-05
126 reads
Grant takes a few lessons for database DR from a nuclear accident in the US.
2022-08-06
100 reads
When a disaster occurs and your staff is working on it, what cadence of updates should your customers expect?
2022-08-01
187 reads
By Brian Kelley
I will be leading an in-person Certified Information Systems Auditor (CISA) exam prep class...
EightKB is back again for 2026! The biggest online SQL Server internals conference is...
By HeyMo0sh
Working in DevOps long enough teaches you two universal truths: That’s exactly why I...
Hi all, I just started using VS Code to work with DB projects. I...
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
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