I am considering a table schema design for a project. The design involves a Many-to-Many Relationship.
The 2 related tables are:
A Class can have many Subclasses, and a Subclass can have many Classes.
Here is my Normalized design:
Is it best to always do this design? The relationship will have 20 rows max. Is it then better to create a single denormalized table as it will then be much easier to update and delete data?
In the Normalized design I would have to create a View to join the tables to display data. And also to create sprocs or triggers to update the base tables.
The denormalized design involves updating/deleting/selecting from a single table.
Is it always best practice to use normalized design?