No, Accelerated Database Recovery Doesn’t Fix NOLOCK.
I have never seen a T-SQL feature that people love as much as NOLOCK.
2025-10-15
Accelerated Data Recovery (ADR)
Accelerated Database Recovery enhancements in SQL Server 2022
We are excited to share that there are several Accelerated Database Recovery enhancements in SQL Server 2022.
2023-12-01
Improving SQL Server Performance and Availability with Accelerated Database Recovery
For many businesses, database performance and availability are crucial elements. A database crash or a lengthy transaction can cause a lot of downtime and have a negative effect on business operations. However, with the introduction of Accelerated Database Recovery (ADR), Microsoft SQL Server has added a potent new feature that greatly enhances database availability and […]
2023-05-02 (first published: 2023-04-03)
2,735 reads
2023-03-10
360 reads
2023-02-24
321 reads
2023-03-20 (first published: 2023-02-10)
404 reads
Blogs
In-Person CISA Training – April 13-16, 2026
By Brian Kelley
I will be leading an in-person Certified Information Systems Auditor (CISA) exam prep class...
EightKB 2026
EightKB is back again for 2026! The biggest online SQL Server internals conference is...
The FinOps Lifecycle: From Budgeting to Reporting
By HeyMo0sh
Working in DevOps long enough teaches you two universal truths: That’s exactly why I...
Forums
VS Code, Unresolved References.
Hi all, I just started using VS Code to work with DB projects. I...
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
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