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,770 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,624 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,173 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,764 reads
2020-10-12
1,995 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,230 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,531 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,692 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,377 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,514 reads
Blogs
Finding the Last Last Name in SQL: #SQLNewBlogger
By Steve Jones
I wrote a piece on the new SUBSTRING in SQL Server 2025 and got...
SQL Server 2025 GAs Today
By Steve Jones
If you aren’t watching the Ignite keynotes today, then you might have missed the...
Run SQL Server 2025 and SQL Server Management Studio on macOS Tahoe
Short version You want to get this running as fast as possible. Do these...
Forums
Email change does not work
I changed my email address in Edit Profile page, but it has no effect...
The case for "Understanding our business" training
Comments posted to this topic are about the item The case for "Understanding our...
Specifying the Collation
Comments posted to this topic are about the item Specifying the Collation
Question of the Day
Specifying the Collation
I am dealing with issues on my SQL Server 2022 instance related to collation. I have an instance collation of Latin1_General_CS_AS_KS_WS, but a database collation of Latin1_General_CI_AS. I want to force a few queries to run with a specified collation by using code like this:
DECLARE @c VARCHAR(20) = 'Latin1_General_CI_AS'
SELECT p.PersonType,
p.Title,
p.LastName,
c.CustomerID,
c.AccountNumber
FROM Person.Person AS p
INNER JOIN Sales.Customer AS c
ON c.PersonID = p.BusinessEntityID
COLLATE @c
Will this solve my problem? See possible answers