Normalized design benefits

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 Mon Mar 12 2001 - 17:28:35 CST