title: Table design for master data
body: <p>I have an asp.net application that uses a lot of master data like Currencies, countries,cities and a lot of other domain specific master data. The current database model has one master table for each type of master data. For example countries have a separate master data table with an ID and a value column. Similary for all the other master data. Is this a right way to manage master data? I am open to completely change it. I would like to get some opinion on it. Also is there any articles or books that would prepare me for such scenarios in db modeling?</p>