Mind your Database Ps and Qs
Louis Davidson explains why a little database courtesy goes a long way.
Louis Davidson explains why a little database courtesy goes a long way.
SQL Server 2016 brings a new feature called Stretch Database, which allows a database to keep transactional data on local instance and warm and cold data on the Azure SQL database platform.
Paul White explores some less well-known query optimizer features and limitations, and explains the reasons for extremely poor hash join performance in a specific case.
Erin Stellato of SQLskills shows how to use Extended Events to monitor for query plans with certain characteristics, such as joins missing predicates, columns missing statistics, and unmatched filtered indexes.
In this article I go through the installation and configuration processes of my Baseline Collector Solution.
If you're making a report from table-based data, an MS Word document is often a good option. In the second part of his introduction to SQL Server best-practice monitoring, Laerte Junior shows how to use PowerShell scripts to create a Word-based report with colour-coded alerts where there are problems or best practices aren't being followed.
Learn how a new feature in SQL Prompt 6.4 can help you avoid costly mistakes in coding.
David Fitzjarrell looks at how and why to use a feature called Automatic Column Group Detection to recognize column dependencies and create extended statistics on recognized groups in Oracle 12.1.0.2.
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...
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