If you want, you can use Delcaritive Referential Integrity (DRI) to enforce restricts. Include a REFERENCES constraint in you table definition.

As you found out, SQL Server does not have any built in way to cascade deletes or updates. Which is good for me because I one of those people who believes that you shouldn't change primary keys.

> I don't know how to cascade parent key changes to children when it is more than 1 parent record being changed.


That's a good problem. There's nothing to link the Inserted and Deleted tables if you've changed the primary key. Is there a candidate key that can be used to relate the children?

-Mike