October 10, 2002 at 3:45 pm
Hi,
I'm designing a database and have a question
about what to do about types and code. In our old system these were all part of a single table that used a code_type column to
segragate all the different codes. In my reading and talking to people almost everyone says to put each different code and type in its own table ie note_type, contact_type, bin_type ect. Is this the way to go it looks much cleaner, but each table now needs its own views and stored procedure to insert and update. Any thoughts on this.
cheers
Randy
October 10, 2002 at 4:21 pm
Can you explain your database to me and what the data is for each type, how they relate what you are doing.
"Don't roll your eyes at me. I will tape them in place." (Teacher on Boston Public)
October 11, 2002 at 1:58 am
As you said, it looks much cleaner, and it is also the correct way of designed a normalized database.
--
Chris Hedgate @ Apptus Technologies (http://www.apptus.se)
October 11, 2002 at 8:49 am
Depending on how these codes are used, how often, and the size of the combined table, it could possibly:
increase concurrency,
reduce overlapping IO calls,
and reduce indexing needs by eliminating the code type column, creating slimmer and better optimized indexes, hence, better and faster execution plans.
If your not gonna help, Please move to the side, because if your not helping the situation, your hurting it....
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply