2015-12-21
325 reads
2015-12-21
325 reads
Louis Davidson explains why a little database courtesy goes a long way.
2015-11-16
230 reads
Whose fault is it if a database is hacked and its contents appear on a hacker’s site? Louis Davidson suggests that, regardless of limitations, the DBA always bears some responsibility.
2014-12-22
161 reads
2014-11-24
167 reads
In opera, tragedy or absurdity happens because the characters are incapable of standing back, and making a difficult decision. Instead, at every stage, they just drift towards their fate by taking the easy option. Don't let the same fate befall you, as a DBA.
2014-08-04
117 reads
As a professional, our knowledge of a given task should extend, at a minimum, one level deeper than is strictly necessary to perform the task. Anything deeper can be left to the ridiculously smart, or obsessive, or both
2014-05-12
122 reads
Louis Davidson on the small dreams that DBAs can nurture, each day, to elevate the drudgery of a seemingly banal task into a celebration of purpose.
2014-03-03
166 reads
Like Sherlock Holmes, a DBA needs the sound deductive reasoning to pinpoint the root cause of a crime, in amongst a thousand interesting but irrelevant details.
2013-11-18
139 reads
Technical debt is frustrating but dealing with it requires patience. Louis Davidson explains why.
2013-09-02
142 reads
It is very difficult to pinpoint what ails a server, just by looking at a single snapshot of the data, or to spot retrospectively what caused the problem by examining aggregated data for the server, collected over many months. The answer? Baselines.
2013-07-22
540 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