There a lot of debates about how to store custom fields in database. Here is some interesting links that help me to get decision (in my case is EVA solution :-)) Storing Custom Fields in the Database (see also comments) - http://blog.springframework.com/arjen/archives/2008/01/24/storing-custom-fields-in-the-database/ Thread from forum - http://osdir.com/ml/bug-tracking.bugzilla.devel/2005-01/msg00191.html Guide to the EAV (FAD) - http://weblogs.sqlteam.com/davidm/articles/12117.aspx http://en.wikipedia.org/wiki/Entity-Attribute-Value_model The circumstances where you would need to go beyond standard row-modeling to EAV are listed below: The data types of individual attributes varies (as seen with clinical findings). The categories of data are numerous, growing or fluctuating, but the number of instances (records/rows) within each category is very small. Here, with conventional modeling, the database’s Entity-Relationship Diagram might have...
ASP.NET tips, problems and solutions discovered during development