 |
 |
Archives of the TeradataForum
Message Posted: Thu, 23 Sep 2004 @ 10:11:21 GMT
Subj: | | Re: Cascade Delete |
|
From: | | Dieter Noeth |
David Clough wrote:
| I'm considering using Cascade Delete for a number of related Order tables. What I want to do it to delete a number (probably in the low
thousands) on Parent entries and for all its dependents to also get deleted - hence Cascade Delete. | |
| My question is, has anyone experienced any significant down side to applying Cascade Delete, such as a significant slow down in Inserts,
etc ? | |
You mean a Foreign Key with "on delete cascade"? You can't specify that in Teradata, there's only the default "on delete restrict".
The only way to achieve this is a Trigger and that won't affect Inserts...
Dieter
| |