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,778 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,629 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,182 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,771 reads
2020-10-12
2,000 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,235 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,538 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,711 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,386 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,529 reads
Blogs
Flyway Tips: AI Deployment Script Descriptions
By Steve Jones
With the AI push being everywhere, Redgate is no exception. We’ve been getting requests,...
A New Word: Fawtle
By Steve Jones
fawtle – n. a weird little flaw built into your partner that somehow only...
Post-quantum key exchange – Insurance policy for your packets
AWS recently added support for Post-Quantum Key Exchange for TLS in Application Load Balancer...
Forums
Where Your Value Separates You from Others
Comments posted to this topic are about the item Where Your Value Separates You...
Fixing the Error
Comments posted to this topic are about the item Fixing the Error
T-SQL in SQL Server 2025: Encoding Functions
Comments posted to this topic are about the item T-SQL in SQL Server 2025:...
Question of the Day
Fixing the Error
On SQL Server 2025, I have a database that has this collation: SQL_Latin1_General_CP1_CI_AS. I decide I want to run this code:
SELECT UNISTR('*3041*308A*304C*3068 and good night', '*') AS 'A Classic';
I get this error:Msg 9844, Level 16, State 4, Line 24 The char/varchar input type uses an unsupported collation. Only a UTF8 collation is supported with char/varchar input type in UNISTR function.What is the easiest way to fix this error? See possible answers