Arthur Fuller
fuller.artful at gmail.com
Sat Mar 14 11:12:33 CDT 2009
Over on the MySQL group, a discussion has been waging about the use of NULLs. One guy in particular is adamant about forbidding them everywhere. He goes so far as to say the existence of NULLs means bad design, pure and simple. I am not quite so radical about it, but I do look askance at any column that permits them, and obviously I forbid them in any FK column. I tossed that in just to take the pulse of this group on this general topic, but my real question concerns something one of the posters wrote: "It seems that someone got bitten very hard in a soft area by a Null one day. On a more practical level, Oracle recommended to design the table with the field where NULLs are to be expected at the end of the table, that saves a little space and two, as the use of indexes is invalidated in case of nulls its is better to place the important indexed fields toward the beginning of the table." I don't know whether this is also true of SQL Server. Do you? Arthur