Sql Server Multiple Cascade Path Issue - Is My Model Faulty?

I have the following model: I want automatic cascade on delete to work - both because it's convenient, keep my data consistent and because it's well supported in Entity Framework

Solution 1:

Now the question is, is there anything wrong with my model?

Not necessarily. Diamond-shaped dependencies are fairly common in database modeling.

The problem is that MS SQL Server doesn't support automatic referential actions on such dependencies, even though they can be a perfectly valid situation from the logical standpoint. In other words, your tool is more limiting than it should be.

You'll have to use triggers to implement cascades.