On Jul 14, 11:06*am, --CELKO-- <jcelko...@earthlink.netwrote:
Quote:
The decision about defaults, constraints and NULL-ability should be
made on the basis of a good data model and not like this. *Trying to
patch up things after an upload is going to eventually fail. *Think of
the old Ford Motors slogan: "The Quality goes in BEFORE the Name goes
on!"
|
Thank you all. Sorry, my initial posting was too sketchy, also I was
fairly new to the environment, less than two weeks, with a monstrous
'master' sql script exceeding 10,000 lines of schema creation, view
creation, sp creation, UDF creation and trigger creation etc. etc...
with very poor comments or minimal comments associating technicality
with business functions, separate documentation is more like user
manual than a real Design Document for a piece of software for the
medical community.
On all columns except key columns being nullable with default values,
my boss told me today because of replication requirement, I've little
knowledge of replication (tried once got people scared, wrongly
thought I might stealing data something...). What's your thought on
the replication thing?
Re: Best practice on nullability and default value 
