marlon.seton (3/21/2013)
By 'why bother' I guess you're meaning why bother using triggers instead of cascade delete? Because the 4GL in which we write the application can't handle FK constraints (and please don't ask why we use such a 4GL, that's a whole other bag of hurt).
That's exactly what I meant. 😉
Ans you seem to have answerede the question yourself. I already gave two examples where specific SQL Server limitations make it impossible or undesirable to use cascading deletes, so that triggers are the next best option. You give a great example where a limitation of another platform has the same result.