Good points. However, I'd caution people to be careful of denormalization -- if you don't normalize in the first place, you run the risk of degrading performance in *other* ways ... not to mention opening the door for some ugly data-consistency issues.
Like all things, there's a balance somewhere. Sometimes, a fully-normalized table structure is the best approach, and sometimes, it isn't. -Brian On Tue, Dec 21, 2010 at 11:03 PM, Dave Newton <davelnew...@gmail.com> wrote: > On Tue, Dec 21, 2010 at 11:56 PM, wrote: > > > Are you sure that database is normalised as well.. > > > > Normalization can often *increase* response time, particularly for some > types of operations, because of the join overhead. The DB needs to be > correct for what it's being used for, and sometimes normalization isn't the > best approach. > > (Although I try to isolate that kind of stuff behind triggers and a > reporting table since that's where I often run in to it. But > over-normalization can be a performance drag under some circumstances.) > > Dave >
