2015-05-01
1,800 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,372 reads
2014-03-27
2,363 reads
2013-06-05
2,453 reads
2013-05-10
2,263 reads
2012-05-11
3,358 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,747 reads
2010-06-17
3,964 reads
2010-04-07
4,057 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
Prime Day Recommendations
By Steve Jones
It’s Prime Day. A few of my recommendations, since I want to do some...
Fabric for Operational Reporting & SQL Endpoint Trap
With Fabric Mirroring, Microsoft is promoting a nice and appealing story for operational reporting...
Crawl, Walk, Run with Agentic Development of Power BI Assets
If you’ve been watching AI roll through the data community and thinking, “this seems...
Forums
SQL Art, Part 4: Happy 4th of July — A British DBA's Guide to Celebrating a War We Don't Talk About
Comments posted to this topic are about the item SQL Art, Part 4: Happy...
Concurrency and Baseline Control: Level 5 of the Stairway to Reliable Database Deployments
Comments posted to this topic are about the item Concurrency and Baseline Control: Level...
Spending Time in the Office
Comments posted to this topic are about the item Spending Time in the Office
Question of the Day
Multiple Values Inserted
I have this code on SQL Server 2022. What happens when it runs all at once?
DROP TABLE IF EXISTS dbo.Commission GO CREATE TABLE dbo.Commission (id INT NOT NULL IDENTITY(1,1) CONSTRAINT CommissionPK PRIMARY KEY , salesperson VARCHAR(20) , commission VARCHAR(20) ) GO INSERT dbo.Commission ( salesperson, commission) VALUES ( 'Brian', 12 ), ( 'Brian', 'None' ) GOSee possible answers