Missing Data
When we don't have all the information needed to model data, we often use NULL. However, that causes other issues.
2021-04-12
2,780 reads
Joe Celko
Mathematicians and SQL
Georg Ferdinand Ludwig Philipp Cantor is considered the creator of set theory, and his theories are the basis for the naïve set theory you learned in school. But there are lots of other mathematicians you should know, such as Hilbert, Frege, Russell, Zermelo and Dedekind. They made a lot of contributions, too. Hilbert Hilbert is […]
2021-01-19
5,635 reads
Data Element Names and Scoping Rules in SQL
How you name data elements in databases and applications programs has often been a matter of personal taste. Decades ago, when I worked for state government, there is a COBOL programmer who would pick a theme for his programs. The paragraphs and variables would be named based on the current theme. One of his programs […]
2021-01-11
2,186 reads
Stairway to Database Design Level 8: Cursors
This final level to the first landing completes the basics of a SQL database, by explaining what cursors are and why you should never use them.
2020-11-18 (first published: 2011-11-02)
11,785 reads
2020-10-12
2,002 reads
Stairway to Data, Level 4: Temporal Data
Joe Celko tackles the most difficult of all the types of data handled by SQL, temporal data, and explains how to avoid the commonest traps for the unwary programmer
2020-07-08 (first published: 2011-06-15)
11,254 reads
Stairway to Database Design Level 6: Procedure Bodies
Having covered the procedure headers in SQL Server in the previous level, Joe tackles the subject of the contents of stored procedures. In this level, he outlines limitations of TSQL as a procedural language, and what you need to bear in mind when deciding how to use them.
2019-04-03 (first published: 2011-09-21)
13,553 reads
Stairway to Data, Level 1: The Basics
A great deal of the confusion that occurs when a database application is developed comes from a poor understanding of the basics of data. Here, Joe Celko gives a broad coverage of the difficulties you're likely to meet when handling data in databases.
2019-03-26 (first published: 2011-05-12)
20,742 reads
Stairway to Data, Level 2: Numerics
A confusion about the nature of numbers can lead to a number of problems in database applications. Joe Celko gives a simple guide to the subject
2019-03-26 (first published: 2011-05-18)
12,398 reads
Stairway to Data, Level 3: Strings
Character-handling in SQL is not particularly straightforward, and confusion about collation and character encoding is a common cause of problems with searching, joining, and sorting.
2019-03-26 (first published: 2011-06-01)
9,546 reads
Blogs
AI: Blog a Day – Day 4: Transformers – Encoder, Decoder, and Attention
By Vinay Thakur
Continuing from Day 3 where we covered LLM models open/closed and their parameters, Today...
Flyway Tips: Multiple Projects
By Steve Jones
One of the nice things about Flyway Desktop is that it helps you manage...
What DevOps Look Like in Microsoft Fabric
By HeyMo0sh
Microsoft Fabric (not to be confused with the more general term “fabric” in DevOps)...
Forums
Can an Azure App Service Managed Identity be used for SQL Login?
I'm fairly certain I know the answer to this from digging into it yesterday,...
Azure Synapse database refresh
Hi Team, I am trying to refresh the Azure Synapse Dedicated pool from production...
how to write this query?
hi everyone I am not sure how to write the query that will produce...
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