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 |
|
metser
Starting Member
27 Posts |
 Posted - 2005-06-22 : 05:37:36
|
| Hello,I have two tables: Resellers table and Companies table. The relation is many to many, as each Reseller works with many companies, and each Company works with many resellers. I will therefore have to use a connecting table with keys from both tables. However - most of the time I will just have to show the Reseller details, including the companies he works with. My question (finally) is this: Even if it's not very good DB planning, should I skip the Companies table and Connecting table, and store the companies names in a special field in the Resellers tables (separated by a comma) - as I just need to show them? this means I will have repetitive data, but why bother with extracting data from the long connecting table for each query? And - in case I will have to supply information regarding the Companies table (i.e. - which resellers work with SONY, for example), I will search the Resellers table (which will take longer, but will not happen very often)...I hope all this was clear. If not - please let me know and I will try to clarify. |
|
|
spirit1
Cybernetic Yak Master
11752 Posts |
Posted - 2005-06-22 : 05:40:52
|
use a connection table. this is normalized design. it's good.  Go with the flow & have fun! Else fight the flow  |
 |
|
|
|
|
|
Which is the best way to go?