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.

 All Forums
 SQL Server 2008 Forums
 Other SQL Server 2008 Topics
 a data modeling question

Author  Topic 

itmaster
Starting Member

28 Posts

Posted - 2013-09-10 : 19:41:24
Hi,
Can someone please tell me if I have this right.
I have always been taught that you can connect two table if the have a 1 to many relation ship. However, if you have a Many to many relation ship you cannot connect them. In this case you need an intersection table put between them. I have seen though people doing this even though the first two table form a one to many relation ship.
Is there a circumstance where you would do this, without having a many to many relationship.

thank you

itmaster
Starting Member

28 Posts

Posted - 2013-09-11 : 11:36:51
Maybe I put this in the wrong forum? Can it be moved to Database Design and Application Architecture?
Thank you
Go to Top of Page

visakh16
Very Important crosS Applying yaK Herder

52326 Posts

Posted - 2013-09-12 : 16:39:23
you may need a intermediate table in one to many relationships when many part table will have some attributes which is not dependent on each instance of relationship and just depends on its key. In that case to avoid redundancy in repeating values for all those related attributes, you apply normailsation and seperate them out into a its own master table and you will just have relationship in a intermediate table with just the keys from participating tables and any attributes which stands unique for each of the relationship.

------------------------------------------------------------------------------------------------------
SQL Server MVP
http://visakhm.blogspot.com/
https://www.facebook.com/VmBlogs
Go to Top of Page

itmasterw
Yak Posting Veteran

90 Posts

Posted - 2013-09-16 : 13:17:22
quote:
Originally posted by visakh16

you may need a intermediate table in one to many relationships when many part table will have some attributes which is not dependent on each instance of relationship and just depends on its key. In that case to avoid redundancy in repeating values for all those related attributes, you apply normailsation and seperate them out into a its own master table and you will just have relationship in a intermediate table with just the keys from participating tables and any attributes which stands unique for each of the relationship.

------------------------------------------------------------------------------------------------------

Thank you
SQL Server MVP
http://visakhm.blogspot.com/
https://www.facebook.com/VmBlogs




ITM
Go to Top of Page
   

- Advertisement -