2015-05-01
1,807 reads
NULL
Database Design Follies: NULL vs. NOT NULL
It sounds simple enough. Either your column will always have a value or it may not. Yet somehow such a seemingly simple decision can become a never-ending debate where database schema begins to resemble superstition and designing effective tables seems more contentious than you expected it to be.
2016-02-26 (first published: 2014-10-30)
27,468 reads
2014-03-27
2,373 reads
2013-06-05
2,466 reads
2013-05-10
2,283 reads
2012-05-11
3,370 reads
Working with null values in SQL XML
We all know NULL values must be dealt with carefully in T-SQL, but how exactly do you best deal with them in SQL XML?
2010-10-26
27,894 reads
2010-06-17
3,973 reads
2010-04-07
4,064 reads
Accommodating Null Values in SQL Server
The key to working with null values properly is to accommodate them consistently. Learn a few tricks that will help you do just that.
2009-09-16
4,497 reads
Blogs
Architecting Zero Downtime Deployments–Day of Data Boston
By Steve Jones
Here are the resources for my talk at Day of Data Boston. Slides –...
The Book of Redgate:A Prehistory
By Steve Jones
I’ve covered the values in a number of previous posts on the Book of...
Evidence-bound: what AgentDBA will and won’t link
By Arun Sirpal
When the evidence names the database, it says so. When it doesn’t, it stops....
Forums
Split Large Queries in Athena with a Simple Modulo Trick
Comments posted to this topic are about the item Split Large Queries in Athena...
Finding Trailing Spaces
Comments posted to this topic are about the item Finding Trailing Spaces
Question of the Day
Finding Trailing Spaces
I have some data in a SQL Server 2025 database. It looks like this for the dbo.Customer table:
CustomerID CustomerName PreferredName 1 Steve Steve 2 Andy Andy 3 Brian Brian 4 Allan Allan 5 Devin Devin 6 Steve Steve 7 Sally SallyI want to detect which names have a single trailing space. The CustomerName is a varchar() and the PreferredName is a CHAR(). Does this query detect the problem rows?
SELECT
CustomerID,
CustomerName,
PreferredName
FROM Customer
WHERE CustomerName <> RTRIM(CustomerName)
OR PreferredName <> RTRIM(PreferredName); See possible answers