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 |
|
AskSQLTeam
Ask SQLTeam Question
0 Posts |
 Posted - 2003-04-14 : 09:39:38
|
| arindam chakraborty writes "A big problem with cascade updating & deleting :The problem :Suppose I have 6 tables in my database ,all are interrelated with each other .and I have set primary -foreign key relation among all the tables. Now when I insert, update or delete any new row from the master table It should affecton corresponding row in all the child table .So my question is if use cascade style first it will make me to drop the all foreign key constraint ....then may it will work. But bcos of some other reason I don't want to delete foreign key relation....What is best another option to do the job .I am using SQL server.ThanksArindam" |
|
|
X002548
Not Just a Number
15586 Posts |
Posted - 2003-04-14 : 10:43:46
|
| It is my understanding the cascading updates and deletes are FOR the Foreign keys. Not the data. I'll have to reconfirm this with BOL, but as a rule we don't using cascading events. I believe mostly beacuse of the overhead.Does any one have experience with cascading?Brett8-) |
 |
|
|
|
|
|
problem with cascade deleting updating