🗄️ Your Column Has a Default Value – and the App’s Inserted Rows Don’t Get It
A column is given a `DEFAULT` constraint specifically so new rows automatically get a sensible value without every INSERT having to specify it – and rows inserted by the application keep showing NULL (or 0) instead, because a column default ONLY applies when a column is OMITTED from the INSERT statement entirely; an ORM or query that explicitly includes the column with a null/default value in code bypasses the database default completely.
🔎 The Problem
ALTER TABLE Orders ADD CreatedDate DATETIME DEFAULT GETDATE(); -- The default only applies when CreatedDate is OMITTED from the -- column list entirely: INSERT INTO Orders (CustomerId, Total) VALUES (1, 99.99); -- CreatedDate correctly gets GETDATE() here. -- But most ORMs generate INSERT statements that list EVERY mapped -- property explicitly - including CreatedDate with whatever value the -- C# object had (often null/default(DateTime)) at the moment of -- insert: INSERT INTO Orders (CustomerId, Total, CreatedDate) VALUES (1, 99.99, NULL); -- The column default is bypassed entirely - NULL is what actually gets -- stored, because the column WAS specified, just with a null value.
✅ Fix: Decide Where the Default Actually Belongs
- If the value should always come from the database (server-side timestamp, a computed default), configure the ORM/entity mapping to EXCLUDE that column from INSERT statements entirely (e.g., EF Core’s `ValueGeneratedOnAdd()` combined with the property not being set in code) so the database default actually gets a chance to apply.
- Alternatively, set the value explicitly in application code at the moment of insert (`CreatedDate = DateTime.UtcNow`) and treat the database DEFAULT purely as a safety net for INSERTs that come from OUTSIDE the app (manual scripts, other systems) rather than relying on it for the app’s own normal path.
⚠️ How to Confirm This Is What’s Happening
- Turn on SQL query logging for the ORM (EF Core’s `LogTo` / sensitive data logging, or SQL Profiler/Extended Events) and look at the actual generated INSERT statement – if the column appears explicitly in the column list, the default is being bypassed regardless of what the constraint says.
A column default is a promise for what happens when you say nothing – the moment your INSERT says something, even NULL, that promise doesn’t apply anymore.

