Apologies, I know this is basic database structures but I'm struggling with a few scenarios. I'm building out a case management solution for IT faults and there are several situations where I don't know whether or not an attribute should be it's own table.
For example 'incident status', this would be a small list of case states (New, In Progress, On Hold, Pending closure, Closed), I can't at this time think of any attribute beyond 'name' and would normally just have this as an attribute of the 'incident' table, but in my current commercial application this is a separate table... am I missing something?


Report
All responses (
Answers (