I am not really asking that I should use RDBMS or config file for 100% of my application configuration, But the configuration type is best addressed by each method
For example, I have heard that "any kind of configuration that can not be changed by the end user" rather than the database The config file must be in. this is right?
I think it is very beneficial to keep the configuration in the file during development.
This is a file (web.config, App.config, or some custom file) and changes that are taken instantly when the code is run. Working with a stored database in a database involves a slight friction. If your team uses a single development database, then you can easily influence other team members with your changes, and if you have different databases then get the latest "Get the latest" And with the latest configuration, flexibility of XML makes the relational stock more natural, compared to any relational DB, plus the "name-val" pair in the file A.
The drawback is that you want to re-use the configuration in my own case in the multiple app or web site instances, we have any configuration file in any known location that any application Can be referred by.
At least, we store the "static" configuration which should not be that the system-updated user settings at runtime are probably more favorable for storage in DB.