Jeff Moden (1/30/2010)

---

None the less, the way nulls have been defined in SQL Server as a default is that they are treated as unknown and X=X where X is NULL,...

Jeff Moden (1/29/2010)

---

to me, NULL means "UNKNOWN" and can have a lot of value compared to zero or an empty/blank string. For example, NULLs are eliminated by aggregates and...

I think you are asking the wrong question. Information can always be represented either with or without nulls. When designing a database you have to make a choice about whether...

You could also use EXCEPT. This query returns any rows in B that aren't also in A:

SELECT * FROM B

EXCEPT

SELECT * FROM A;

Jeff Moden (1/23/2010)

---

I'd...

RBarryYoung (1/23/2010)

---

David Portas (1/22/2010)

---

All the conventional Normal Forms apply exclusively to relations with values, never nulls. In fact normalization predates the invention of SQL and nulls. So you can't say...

Nothing personal. I just wanted to set the record straight, keeping in mind your comments about reading what is not there and stretching the meaning of words beyond their author's...

PaulB-TheOneAndOnly (1/22/2010)

---

Bottom line is ... Codd invented everything at the same time - including Null - and the model was good but as it happens in all domains of life...

Intensive byte level operations within large objects are hard or impossible...

PaulB-TheOneAndOnly (1/21/2010)

---

All the conventional Normal Forms apply...

Of course I agree. However in a scenario...

So your only answer to my question is to tell me that I'm not asking the right question. Right...

You can invent an exception to any business rule you care...

PaulB-TheOneAndOnly (1/20/2010)

---

It is obvious that PERSONNEL (which includes managers - actually an attribute of PERSONNEL) and DEPARTMENTS are two different entities that must be modeled then physically implemented as two...

What is "wrong" with...

Why?

It is true that such relationships between...