DMV Comparison for SQL Server 2019 vs Azure SQL Database
What DMVs were added to Azure SQL Databases, and which DMVs are missing from Azure SQL Databases but still exist on SQL Server 2019 or other versions?
2025-06-02
What DMVs were added to Azure SQL Databases, and which DMVs are missing from Azure SQL Databases but still exist on SQL Server 2019 or other versions?
2025-06-02
2023-12-27
487 reads
2023-12-21 (first published: 2023-12-20)
497 reads
This is a great wrapper for your DMV's to automate a quick performance metric capture.
2016-01-12 (first published: 2016-01-06)
438 reads
Performance monitoring and optimization is an inseparable part of a DBA's activities. To optimize a poorly performing system/query or to troubleshoot the performance issues you need to know the root cause. Prior to SQL Server 2005, we had several system tables to monitor the state of the system.
2010-04-06
2,169 reads
2010-03-04
3,295 reads
Get a free green paper, an early access look at a new DMV book from longtime author Ian Stirk.
2010-02-02
3,224 reads
2009-06-30
3,203 reads
2009-06-22
2,878 reads
2009-06-15
3,140 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