L' Eomot Inversé (1/28/2013)

---

Sean Lange (1/28/2013)

---

Lowell (1/28/2013)

---

in our case, we have a config file that has the connection string information, and a single row table that contains a lot of settings relevant to the application that uses that database.

I don't think you really want to store the connection info in the database, without also storing it outside of the database(how would you open teh conneciton to read the connection info) , but application type settings, you bet.

I too have this type of setup in a number of applications. I have also added an instead of trigger to most of these applications to prevent adding/deleting. It can only have 1 row. 😀

On single row tables, count me in - they are often useful; but rather than a trigger I use a check constraint on a column used as the primary key (checking that the value is 0). I know it seems crazy to bother with a primary key for a table that will have only one row, but I don't like tables without primary key and in conjunction with a check constraint it is a safe way to enforce the one row only requirement.