2004-10-12
2,323 reads
2004-10-12
2,323 reads
Part 2 of Steve Jones' Incident Response series that looks at how you should be prepared as well as what to do when disaster strikes. Part 1 established a basic framework and part 2 dives deeper into what you might need for the next virus, hardware failure, or hurricane :(.
2004-10-11
4,922 reads
Working with a QA server in SQL Server 2000 is something everyone should learn to do. Having some staging area between development and production will help ensure a more stable environment and smoother deployments. After a little hiatus, Steve Jones continues with this series looking at moving the latest backup over to QA.
2004-09-29
6,561 reads
It was an adventure. Moving a SQL Server physically from one location to another should be a simple process, but it turned out to be a bit more than Steve expected. Read about the adventure and inject a little humor into your day.
2004-09-24
5,223 reads
2004-09-24
2,531 reads
2004-09-23
1,945 reads
2004-09-21
2,286 reads
2004-09-20
2,482 reads
2004-09-16
2,384 reads
What happens to SQL Server 2000 indexes over time? Fragmentation is one of the effects and Steve Jones looks at how you can work with and identity fragmentation.
2004-09-15
16,186 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