I am writing a Client/Server application with an SQL backend. I am having some trouble figuring out how to store some common application wide settings in the database.

For instance. I need to save a password for gaining access to the "Admin Console". The way I am doing it now is a dedicated table that has only a single row with a column for each setting. This is method seems yukky to me.

I thought about using my.settings avaliable in the .NET framework, but these settings will not work there because each station has to use these same settings, and my.settings can differ per installation.

Perhaps a better method is to create a Settings table with a text "Setting" column, and text "Value" column. So it would store those individual settings like that.

That seems like a much better method than what I am doing now at least. What do you think?