If your using MS SQL, views do a good job of this too. You can consolidate
your normalized data in a central location and still keep your ever
expandable normalized database. Best of both worlds.
Rick
-----Original Message-----
From: Dave Watts [mailto:[EMAIL PROTECTED]]
Sent: Friday, December 15, 2000 12:08 PM
To: CF-Talk
Subject: RE: how many milliseconds is too many?
> This may not apply to your situation, but it is worth investigating.
>
> Consider creating a shadow database (possibly denormalized) to
> address the performance issue...
>
> ....organize the data to fit the specific processing requirements of
> your most frequently used queries. Then take advantage of stored
> procedures, caching, etc to reduce processing to the absolute minimum.
>
> To the purists, this may be heresy. But if the success of the site
> depends on the performance, it may be critical to depart from "pure"
> database design tenets, waste some storage... but get the job done.
>
> I am reminded of a quote from my years at IBM:
>
> "A job worth doing, is worth doing poorly... if there is
> no other choice"
You're correct - sometimes there's no other choice.
However, this step shouldn't be taken lightly. Very often, when I see people
working with denormalized data, and I ask them about it, they say "we did it
this way for performance", even though they could have gotten the
performance they needed without denormalization - they just didn't know how
(or know better).
Dave Watts, CTO, Fig Leaf Software
http://www.figleaf.com/
voice: (202) 797-5496
fax: (202) 797-5444
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
