Hi, Bret-

I really don't know the answer to your question. It could be that it would more efficient for you to write your own cascade delete in this--at least to experiment.

The RI is general purpose...and, in my experience, the more general purpose something is, the more code it has that's not needed for a specific case. So, of course, the trade off must be weighed.

Is it a straight delete in the child tables that you need? They aren't related with RI to any tables themselves? If that's the case then perhaps a combination of table buffering and transaction processing is all you need?

>When I leave table1 related to just one of the children, the DELETE FROM table1 takes 15 or 20 minutes

...snip