March 3, 2010 at 1:09 am
Hi,
what is the impact of storing the null values in a table. If there is any issue, what is the alternative for the null.
🙂
March 3, 2010 at 1:29 am
An impact would be that you can't test for an a NULL with = NULL you have to use IS NULL. NULLs are usually excluded from most aggregates.
NULL values have their place, it typically means "I don't know/care". It is useful where you don't want to designate some value to indicate "unknown".. For three state logic you can have yes, no, and I don't know.
CEWII
March 5, 2010 at 3:13 am
hi,
thanks for ur response,
what is "three state logic"?
🙂
March 5, 2010 at 5:25 am
dba-vb (3/3/2010)
what is the impact of storing the null values in a table
Read Below post
http://www.sqlservercentral.com/articles/Advanced+Querying/2829/
You will find "three state logic" Even more than that
-------Bhuvnesh----------
I work only to learn Sql Server...though my company pays me for getting their stuff done;-)
March 5, 2010 at 11:14 pm
dba-vb (3/5/2010)
hi,thanks for ur response,
what is "three state logic"?
True, False, and "Unknown".
The real affect of having NULLs in a table is usually (not always) a thing called "Denormalization" and except for certain reporting tables, it's normally not a good thing.
--Jeff Moden
Change is inevitable... Change for the better is not.
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply