2025-11-07
1,219 reads
Indexes
Index Rebuilds Make Even Less Sense with ADR & RCSI
Accelerated Database Recovery (ADR) is a database-level feature that makes transaction rollbacks nearly instantaneous. Here’s how it works.
2025-02-19
A Tidy Database is a Fast Database: Why Index Management Matters
Learn about the ways in which you might better manage indexes for a better performing and efficient database.
2024-11-11
3,918 reads
Prevent Duplicate Records in SQL using Filtered Index
In this article, I share how an SQL Server filtered index solved the problem of preventing duplicates for new rows in a table.
2024-07-03
SQL Server Resumable Index Operations
The ability to pause and then resume index rebuilds has been added to SQL Server. This is a fantastic feature, and with the release of SQL Server 2019, we can now replicate it on the actual create index process. Learn how to use this feature in this short article.
2023-06-26
12,864 reads
2021-04-27
840 reads
How Bad are Bad Page Splits – The Rest of the Story
In Part 1 of this article we looked at a specific use case (probably exaggerated) that gave us an idea about how CPU and IO performance might be affected by a bad page split. We continue this analysis looking at what really happens to the data on the leaf pages of a clustered index with […]
2020-07-02
4,488 reads
Building SQL Server Indexes in Ascending vs Descending Order
In this tip we look at the impact of building SQL Server indexes in ascending versus descending order and the impact.
2020-02-04
“Included columns” for non-clustered indexes explained
Learn about the advantages and disadvantages of using INCLUDE columns in your index.
2021-04-30 (first published: 2019-09-17)
29,077 reads
Some T-SQL INSERTs DO Follow the Fill Factor! (SQL Oolie)
With origins from the world of “Submarine ‘Dolphin’ Qualification” questions, an “Oolie” is a difficult question to answer, or the knowledge or fact needed to answer such a question, that may or may not pertain to one's duties but tests one's knowledge of a system or process to the limit. Introduction Contrary to what many […]
2019-08-08
6,321 reads
Blogs
Optimising Costs: Strategies for Efficient Cloud Resource Management
By HeyMo0sh
Over time, I’ve realised that one of the hardest parts of cloud management isn’t...
Cost Visibility: Tracking and Analysing Your Cloud Spend
By HeyMo0sh
One of the biggest challenges I’ve faced in cloud operations is maintaining clear visibility...
Whiling away an afternoon, thinking
By Steve Jones
I come to Heathrow often. Today is likely somewhere close to 60 trips to...
Forums
Fun with JSON II
Comments posted to this topic are about the item Fun with JSON II
Changing Data Types
Comments posted to this topic are about the item Changing Data Types
Answering Questions On Dropped Columns
Comments posted to this topic are about the item Answering Questions On Dropped Columns
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