title: Sql design with domain metadata: two tables (one to one) or one table representing different kinds of data?
body: <p>I have an invoice table. </p>
  
  <pre><code>Invoices
  --------
  id
  invoicenum
  description
  amount
  rowversion
  </code></pre>
  
  <p>I need to attach metadata to this table, such as business unit location, last modified by, last modified on, and security access code.</p>
  
  <pre><code>InvoiceMetadata
  ---------------
  id
  BU
  User
  Date
  AccessCode
  rowversion
  </code></pre>
  
  <p>I now have two options. I can just tack these fields onto my Invoices table, or I can create a separate table that logically contains this information. </p>
  
  <p>What factors do I need to consider to make an intelligent decision? My inner programmer says I need to create two tables. My inner DBA says I need to make one. My inner project manager says I need to know what the payoffs are for both options. It is this last inner voice I need help with.</p>