title: Database Design Without Foreign Keys
body: <p>After having worked at various employers I've noticed a trend of &quot;bad&quot; database design with <em>some</em> of these companies - primarily the exclusion of <em>Foreign Keys Constraints</em>. It has always bugged me that these transactional systems didn't have FK's, which would've promoted referential integrity.</p>
  <blockquote>
  <ul>
  <li><p>Are there any scenarios, in transactional systems, whereby the omission of FK's would be beneficial?</p>
  </li>
  <li><p>Has anyone else experienced this, if so what was the outcome?</p>
  </li>
  <li><p>What should one do if they're presented with this scenario and their asked to maintain/enhance the system?</p>
  </li>
  </ul>
  </blockquote>