Don't sacrifice good clean storage of relational data.  Always store it
"correctly" and "cleanly" because you can always dump out "flat" tables
at will and whim later.  But you can't easily go the other way.


We have some tables with several million rows each, and of course
joining across them is painful.  To get speed, we create periodic
"copies" of the data in "flat" (reduced number of wider tables) format,
which helps quick searching.  But we are careful that these are COPIES,
and that our main storage is in the relational tables.

-----Original Message-----
From: Michael Dinowitz [mailto:[EMAIL PROTECTED]
Sent: Monday, July 19, 2004 10:05
To: SQL
Subject: Space vs. Joins


Lets say that a join has to be made between 4 or 5 different tables.
Two or three of these tables can be avoided by creating a column or
two in one table. These columns will usually be blank. Is it better to
have more, tighter tables and join them or to make fewer tables with
more columns even if one of those columns may not have much data?
Not worrying about space, just speed.
Let the debate begin. :)

--
Michael Dinowitz
http://www.houseoffusion.com
For all your ColdFusion needs
________________________________
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings] [Donations and Support]

Reply via email to