title: Using a Single Row configuration table in SQL Server database. Bad idea?
body: <p>In developing a shopping cart application I've found that I needed to save settings and configurations based on the administrator's preferences and requirements. This information can be anything from company information, Shipping account IDs, PayPal API keys, notification preferences, etc.</p>
  
  <p>It seems highly inappropriate to create a table to store a single row in a relational database system.</p>
  
  <p>What is the appropriate way to store this information?</p>
  
  <p>Note: my DBMS is SQL Server 2008 and programming layer is implemented with ASP.NET (in C#).</p>