September 14, 2007 at 7:45 am
Correct Kenneth - and I can see I am guilty of said sloppy use of terms. I'm heading back and removing my own sloppy handling of the terms.
----------------------------------------------------------------------------------
Your lack of planning does not constitute an emergency on my part...unless you're my manager...or a director and above...or a really loud-spoken end-user..All right - what was my emergency again?
September 23, 2007 at 11:19 pm
If you use the design I am suggesting, the PK of the parent table is part of each and every child table. (does this add space to your system? YES!!!) but what you gain is performance. So you don't do a single join. You already have the field as part of the table.
What you lose is performance.
My experience shows that selecting from a view performing 5 joins is faster than from the table created by statement
SELECT *
Into TheTable
FROM TheView
Adding space means more reads from disks. More memory used per query. Less number of queries fit in memory. More physical reads, less logical reads.
_____________
Code for TallyGenerator
Viewing 2 posts - 16 through 16 (of 16 total)
You must be logged in to reply to this topic. Login to reply