Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Issue setting Foreign key constraint
Message
 
General information
Forum:
Microsoft SQL Server
Category:
Other
Miscellaneous
Thread ID:
01518536
Message ID:
01518540
Views:
29
>>>>Hi,
>>>>
>>>>When creating a FOREIGN KEY constraint in SSMS I get message that:
>>>>
>>>>….  may cause cycles or multiple cascade paths. Specify ON DELETE NO ACTION or ON UPDATE NO ACTION, 
>>>>or modify other FOREIGN KEY constraints.
>>>>
>>>>
>>>>If I understand correctly the problem is that the table where I am attempting to set a Foreign key constraint has a dependency on some other table that creates a conflict. My tables have many links. So my question is, how can I find out which table has a link to this table that I need to change? How do I find out?
>>>>Thank you for any other suggestions.
>>>
>>>Can you find a key which is in turn a foreign key in another table? I think this message tells that you have a chained relationship and setting CASCADE option may be problematic.
>>
>>The table has many foreign keys. I am trying to figure which of the "other" tables where this table has a foreign key "causes" the problem. But I will strart looking into every one of them and see if I can spot what to change.
>>Thank you.
>
>BTW, when you were creating this constraint, you created it for the specific key? So, start from that key first.

I am confused. How can I create a constraint NOT for a specific key? What I did is
1. Created foreign key constraint on field MyField1
2. Created foreign key constraint on field MyField2
and so on.
but when I try to do it for some field MyFieldN I was hitting the problem.
"The creative process is nothing but a series of crises." Isaac Bashevis Singer
"My experience is that as soon as people are old enough to know better, they don't know anything at all." Oscar Wilde
"If a nation values anything more than freedom, it will lose its freedom; and the irony of it is that if it is comfort or money that it values more, it will lose that too." W.Somerset Maugham
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform