How to lay out SQL Code
Anyone who inherits a database application dreads poorly laid-out SQL code. Development teams loathe it. Putting it right would be easier, if there was a common, agreed, standard in place, so why the difficulty?
Anyone who inherits a database application dreads poorly laid-out SQL code. Development teams loathe it. Putting it right would be easier, if there was a common, agreed, standard in place, so why the difficulty?
Keeping track of your DDL is something that is critical and some sort of VCS system should be used. However pulling out your scripts from SQL Server sometimes entails a bit more than the standard scripting. New author Richard Sutherland brings us an open source project that can help you get this done. Complete with code.
In this tip we look at the process of installing Reporting Services on a server that is already running Database Services.
Learn about SQL Server memory needs and settings including RAM amounts, how to enable AWE, maximum server memory and the differences of 32- and 64-bit platforms.
A woman sues Best Buy for $54million. That's absurd, but her laptop is worth more than the hardware.
A woman sues Best Buy for $54million. That's absurd, but her laptop is worth more than the hardware.
By HeyMo0sh
Over time, I’ve realised that one of the hardest parts of cloud management isn’t...
By HeyMo0sh
One of the biggest challenges I’ve faced in cloud operations is maintaining clear visibility...
By Steve Jones
I come to Heathrow often. Today is likely somewhere close to 60 trips to...
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
Comments posted to this topic are about the item Answering Questions On Dropped Columns
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