Is it a good idea to have a single STATUS table if we have to store multiple status in the data mart?

[Hemapr]

We have a situation that we need to have different types of status tables like Alarm Status, Ticket status and so on. There are atleast 5 status tables that we need in the data mart. Each status table has < 10 rows.
So, is it a good idea to create these status as 5 different tables or create 1 single STATUS table and identify different status type with a Type column in the status table.
Here is the design with a single Status table:

Status
--------
Status_ID (PK)
Status_Type (Alarm/Ticket/Flash etc)
Status_Code (If its Alarm then code = High)


Question : Is it a good idea to have a single STATUS table if we have to store multiple status in the data mart?

[hang]

No, I don't think it's good idea in DW modeling. You should either group low cardinality status into junk dimensions or leave them in their respective standalone lookup dimensions if cardinality is not low. By having a single generic dimesion, you don't gain anything but to have a confusing model.

[BoxesAndLines]

Exactly. This is a bad idea in OLTP models as well as dimensional models.

[Sponsored content]