Distinguish 1:M association Vs 1:M composition in SQL

Viewed 498

How can I distinguish a 1:M association versus a 1:M composition when adding a FK to my table?

For example, I use the query statement below to alter an existing column Account (in Case table) to a foreign key that references AccountId (in Account table).

They share a 1:M associative relationship where one account can have many cases. What if they had a 1:M composition, how would this alter statement look like? Is the statement below correct for a 1:M association?

Alter table [dbo].[Case] with check add constraint [FK_Case_Account] foreign key ([Account]) 
references [dbo].[Account] ([AccountId])
GO

Alter table [dbo].[Case] check constraint [FK_Case_Account]
1 Answers
Related