Approach to mapping dictionary database tables to models in MVC

Answer 1

If it's just going to be a set of constants that are contained in the database instead of code, you could have a static class load the status constants for everyone else to use. That way there's no duplication between db and code, and no magic numbers.

edit: since it's a static class, you could have it lazy load the constants. Don't hit the database until the first time someone asks for a status value.

Answer 2

I'd say if you going to change it often it's better to go with table. Otherwise static class is fine (for example no point having table to store sex, or list of states).