natural language is not the best fit for the world of computers.

I sometimes need to demo detailed and very technical testing scenarios and sometimes training. And no matter how...

I found the Microsoft Certified Pro courses to be very useful

Answer the newbie/basic questions with links? then all you need is a standard suite of links you can reuse over and over again. And the poster will likely...

More nonsense....

I give up. 🙂

that question implies that you would otherwise have ~10000 "nullable" columns in your design?

which would be nonsense design under any stretch of the imagination, wouldn't it?

why do the same flawed arguments keep popping up?

[[If you deal with a report and want all columns via left joins, then there will be nulls. ]]

We don't know the...

funny, they don't have all the problems you mention for licensing of plumbers, electricians, doctors, lawyers, accountants, etc. etc. etc.

wonder why you are so convinced it would cause the world...

unfortunately, our profession does not have any licensing standards.

anyone can claim to be a programmer. anyone can claim to be a database "developer" or designer, or database "engineer"...

Correct, and that is NOT a requirement for a schema that disallows nulls. why would you possibly think it was?

[[The debate might be over nulls, but the pain might actually be missing or unknown business requirements.]]

One could argue that allowing nulls facilitates poor definition of requirements. Not to...

[[that it adds code complexity]]

Nah,

try rating 1000 reports where you have to "if isnull blah, blah, blah " a pile of columns for null because it's the "programmer's choice" what...

one problem with that thinking is that sql server does not handle "null" flag consistently. it screws up grouping, screws up string handling, sorting, even keys etc. etc.

Just one example...

Is there some thinking that there is no difference between a REPORT (extracting, analyzing, formatting, and displaying datato a user) and RELATIONAL DATA PERSISTENCE?

They are not the same thing!...

[represent having no value]

it was in earlier post. put nullable column into it's own table, enforce 1 to 1 relationship to parent table.

no data for a row in parent...

heck why not use bigint?

and then someone will ask you to write a report to see all the records that have certain of those encoded values.

So then are you going...