What are the tips/techniques when you need to persist classes with inheritance to relational database that doesn\'t support inheritance?
Say I have this classic exam
Be careful with database inheritance in certain situations - we implemented it in our application for our auditing strategy and we ended up with a performance bottleneck/nightmare.
The problem was that the base table we used was insert only and rapidly changing so what we ended up with were deadlocks all over the place. We are currently planning to break these apart into their own tables because the headache of having the same columns in 15 different tables versus a performance nightmare is well worth it. This was also compounded by the fact that the entity framework doesn't necessarily handle inheritance efficiently (this is a known issue by Microsoft).
Anyway, just thought I'd share some knowledge since we've been through the wringer on this issue.