Technical Article

Handling NULL values in SQL Server 2005

In the simplest terms, a NULL value represents an unknown value. It's unknown in the sense that the value is: missing from the system, may not be applicable in the current situation, or might be added later. NULL values are different than any other value and are sometimes hard to compare and handle.

SQLServerCentral Editorial

Opening Day

Today is the opening day for the PASS conference here in Denver and it's kind of exciting. As many of you read this, I've hopefully gotten Simon Galbraith, owner of Red Gate software, and my boss, out here at the ranch shoveling manure. He's anxious to get on the ATV for a ride, so maybe I can work out a deal to reduce my workload πŸ™‚

SQLServerCentral Article

From DBA to DWA

Everyone wants to know what a DBA does and it is becoming a hard question to answer as the responsibilities and capabilities of database platforms increase. Longtime author Vincent Rainardi brings us the proposition of a new type fo DBA, one that focuses more on data warehousing.

Blogs

AI: Blog a Day – Day 4: Transformers – Encoder, Decoder, and Attention

By

Continuing from Day 3 where we covered LLM models open/closed and their parameters, Today...

Flyway Tips: Multiple Projects

By

One of the nice things about Flyway Desktop is that it helps you manage...

What DevOps Look Like in Microsoft Fabric

By

Microsoft Fabric (not to be confused with the more general term β€œfabric” in DevOps)...

Read the latest Blogs

Forums

Can an Azure App Service Managed Identity be used for SQL Login?

By jasona.work

I'm fairly certain I know the answer to this from digging into it yesterday,...

Azure Synapse database refresh

By Sreevathsa Mandli

Hi Team, I am trying to refresh the Azure Synapse Dedicated pool from production...

how to write this query?

By water490

hi everyone I am not sure how to write the query that will produce...

Visit the forum

Question of the Day

Fun with JSON I

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 *
FROM OPENJSON(
     (
         SELECT t.* FROM #test_data AS t FOR JSON PATH
     )
             ) t;

See possible answers