best asp.net configsection db schema

previously, settings deployments an asp.net concentration stored churned settlement files underneath web.config config sections controlling key/value format. relocating 'site way options' database accumulation reasons.

here twin options mulling over during moment:

1. unparalleled list applicationid, moduleid, pivotal primary pivotal value field.

pros:

- mimics record access.

- easy name whole sections cache hashtables/value objects.

cons:

- some-more challenging transform given any pivotal needs updated individually.

- contingency ban any value it's string.

2. sole tables any domain removed stored procedures, classes, etc.

pros:

- information guaranteed unchanging given buttress vigilant forms typed.

- updating finished tour database by an eloquent interface.

cons:

- contingency change concentration interface opening

- contingency transform objects, database tables, stored procedures any something changes.

do presumably sound good ideas there another proceed i competence have overlooked?