Designing table with increasing number of columns frequently

Question

I am looking to redesign a table which is hit frequently by adding new columns as new busness requirements come in. Every time a new column is added,  it need to change many db objects realted to this table/views/stored procedures. Can I define column names in a table and store the values in a different table, so when ever i create a new column I just add it only to this new table. Do we have any frame work/patterns/best practice to handle this efficiently ?

Answer 1

Hi,

Take a look at EAV model:

http://en.wikipedia.org/wiki/Entity%E2%80%93attribute%E2%80%93value_model

http://weblogs.sqlteam.com/davidm/articles/12117.aspx

---

Regards,

Asim Bagwan

Kindly mark the replies as Answers if they help!