NULL

SQLServerCentral Article

Database Design Follies: NULL vs. NOT NULL

  • Article

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.

4.38 (78)

You rated this post out of 5. Change rating

2016-02-26 (first published: )

27,166 reads

Blogs

Fabric as a Data Mesh Enabler: Rethinking Enterprise Data Distribution

By

For decades, enterprises have approached data management with the same mindset as someone stuffing...

Truncate Table Pitfalls

By

 Truncate Table Pitfalls Truncating a table can be gloriously fast—and spectacularly dangerous when used carelessly....

dataMinds Connect 2025 – Slides & Scripts

By

You can find all the session materials for the presentation “Indexing for Dummies” that...

Read the latest Blogs

Forums

DBCC CHECKIDENT

By Steve Jones - SSC Editor

Comments posted to this topic are about the item DBCC CHECKIDENT

Distributed Availability Group Health: T-SQL and Zabbix

By Pablo Echeverria

Comments posted to this topic are about the item Distributed Availability Group Health: T-SQL...

extended events to spy on our server between 8 and 9 am

By stan

Hi, our peer who owns a remote mysql server from which we extract warehouse...

Visit the forum

Question of the Day

DBCC CHECKIDENT

What is returned as a result set when I run this command without a new seed value?

See possible answers