Re: Normalized design benefits

jay,

"they have moses and the law. if they do not believe these, they will not believe even if someone came back from the dead".

articles and references are useful only in academia. simply document your concern and then be as supportive as you can of the team without criticizing or being contradictory with other team members. like it or not, much of the workplace is still about "do i like you" rather than "do you know what you are talking about". you can "prove you are right" and still be dismissed, since relationships are not about "being right", but "being likeable".

just curious....has anyone referred to you as being "anal" or "inflexible" or "perfectionist" ? if so, polish up your resume and start looking...and always remember...

"life is about relationships" (Steve Long, Apr 1999)

> Jay Canha wrote:
> >
> > Some members of our project design team have a perception that
> > normalized transactional databases take longer to
> > desing/develop/maintain than denormalized designs and, therefore,
> > normalization isn't really worth doing. This is leading to a string of
> > denormalized databases which concerns some developers familiar with the
> > benefits of a normalized design.
> >
> > Can anyone point out any some articles by respected authorities which
> > explain (in basic terms) the benefits of normalization and prove that
> > normalization actually saves time and effort.
> >
> > Thanks.
Received on Sat Apr 21 2001 - 03:56:18 CEST