Configuration vs Database storage -

i keep short, looking store product plan data, these plans users pick payment options. data include how plan cost , unit details of plan are, makes unit (day/week/month) , simple data plan. these plans may or may not change once month or once year, company start , things changing on 11th hour , contently there no real way predict when change. co-worker , discussing whether these values should stored in web.config (where are) or move them database.

i have done googling , have not found resource draw clear line of when should in database or in web config. wanted know thought on , see if define when data should stored in config or in database.

thanks help!

from brief description provide, seems me configuration data, eventually, may accessed not web server-based application running on 1 computer, other supporting applications, such end-of-month batch jobs, may want run on other computers. support possibility, idea store data in sort of centralized repository can accessed remotely multiple computers.

storing configuration data in database obvious way meet requirement. if don't want that, approach store configuration data in file on company-internal (rather public) web/ftp server. application can use utility such curl retrieve configuration file web/ftp server.

of 2 approaches, think using database best, because provides ergonomic way not read configuration data, update it.