SAN and NAS protocols and how they impact SQL Server
Discusses the various SAN and NAS protocols (FC, iSCSI, NFS) and how choosing one over the other can impact your SQL Server Performance.
2015-07-24 (first published: 2012-04-24)
18,235 reads
Discusses the various SAN and NAS protocols (FC, iSCSI, NFS) and how choosing one over the other can impact your SQL Server Performance.
2015-07-24 (first published: 2012-04-24)
18,235 reads
This article attempts to explain RAID's impact on SQL performance.
2014-05-16 (first published: 2012-05-01)
37,997 reads
Discusses the use of the newly introduced APPLY Statement in SQL Server 2005
2009-02-27 (first published: 2008-06-16)
24,982 reads
Discusses Index Selection impact when functions are wrapped around WHERE clause filtering columns
2008-02-28
16,011 reads
This article describes one method of implementing a reporting system in SQL Server 2005
2008-01-21
14,083 reads
New Author! The first of two articles this week on fill factors, this article looks at the impact fill factor can have on performance and shows you the key tools and counters you use to assess the impact of changes to fill factor.
2003-11-19
25,943 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