If I understood you correctly, you would like to save and load your configuration settings to the database instead of a configuration file? In such case I guess you would have some database table for storing the settings. You can map it to a class and use that class as a configuration settings repository. You would utilize it the way you perform the normal CRUD operations with OpenAccess ORM. For code samples you can also download the OpenAccess SDK.
In addition, feel free to build your own logic on top of the class depending on the specifics of your scenario. For instance, if you are storing the settings in only one row (each column being a separate setting), you can create a derived or composed singleton implementation to ensure that your application is accessing the first row only.
Let me know if my assumption was wrong or in case you need any further clarifications.
the Telerik team
Telerik OpenAccess ORM Meets ASP.NET Web API. Read more.