INSERT worked despite NOT NULL constraints

---

INSERT INTO Sales.SalesTerritory (
	[NAME],
	CountryRegionCode,
	[Group])
VALUES (
	'Pacific Islands',
	'US',
	'North America');

Why didn't the INSERT fail? To some extent, I understand. A subsequent query reveals that attribute values not provided in the INSERT are indeed NOT NULL. But how did that happen?

Take the SalesYTD attribute for example. The query shows a value of 0.00. Is the answer to my above question in the following screenshot?

Alan,

You were on the right track. The query succeeded because the money datatype defaults to zero when not provided. Many people despise the money datatype, preferring to use one of the integer datatypes instead for that behavior and a few other inconsistencies with mathematical operations against it.

Thanks,

Don