Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
arkiboys
Master Smack Fu Yak Hacker
1433 Posts |
 Posted - 2009-11-11 : 05:58:28
|
| Hello,There is a table i.e. table1 which has 20 fields.There are about 6 lookup tables which are joined to table1 via their ID fields...Forexample the FK are in table1 and the keys are in the lookup tables so the table is normalized.On average, around 50, 000 records are added to this table.This table i.e. table1 is used for reporting.Question:Should I use ID fields in table1 to join to the lookup tables as I am doing now (Normalized) or should I just place the actual text of the lookup tables inside table1 (NOT normalized). I wonder if designing the table1 this way, will improve on the speed of the reporting when the table is very large...What do you think?Thanks |
|
|
yosiasz
Master Smack Fu Yak Hacker
1635 Posts |
Posted - 2009-11-11 : 10:17:10
|
| yes it will improve if you have indexes, if they are clustered or not, etc. just having FK and IDs in of itself will not speed things up. your design approach sounds solid to me.<><><><><><><><><><><><><><><><><><><><><><><><><>If you don't have the passion to help people, you have no passion |
 |
|
|
arkiboys
Master Smack Fu Yak Hacker
1433 Posts |
Posted - 2009-11-11 : 10:31:29
|
| Just to confirm, you mean I should have the table un-normalized and Not IDs which refer to the lookup tables?Thanks |
|
|
|
yosiasz
Master Smack Fu Yak Hacker
1635 Posts |
Posted - 2009-11-11 : 10:35:45
|
| I am saying use normalized and use IDs<><><><><><><><><><><><><><><><><><><><><><><><><>If you don't have the passion to help people, you have no passion |
|
|
|
arkiboys
Master Smack Fu Yak Hacker
1433 Posts |
Posted - 2009-11-11 : 16:08:19
|
| Thanks |
|
|
|
|
|
|
reporting design