Lookup Tables Best Practices: DB Tables… or Enumerations

Question

If we have to store the available positions at a company (i.e. Manager, Team Lead, ... etc). What are the best practices for storing it? I have two opinions with comments...

Answer 1

Lookups, Lookups, Lookups (insert monkey-dancing video here)

My personal "best practice" is to have everything in the database. Positions in a company is definitely a lookup table.

The same goes for translations, which may be a bit trickier, but generally a view definition joining the table with a translation table is a good start.

Besides, if the Position is only an int value, and your app is single-language, you can add the position titles directly to the database.