Like punkouter said, a configuration file is a good option. If you want to store it in your database, you can also do that. I developed a basic layout for our database system that contains some default tables, views, stored procedures and functions that
we apply to each of our databases. Before designing a new database, we first run a SQL script that creates these objects. One of the default tables is _ExtendedProperties, which is used to store single pieces of information. It has 2 fields: Key (NVARCHAR(MAX))
and Value (NVARCHAR(MAX)) and it's basically a dictionary. Of course it only contains string values, but that's usually OK. It is not used very often, but it is handy for cases like yours, where you want to store loose values.