title: How to denormalize a heavily normalized database system?
body: <p>I'm looking to introduce some database denormalization to a heavily normalized system.</p>
  
  <p>I have a large set of databases that have evolved over ten years and are under increasing amounts of load so I'm looking to improve PERFORMANCE and possibly reduce the complexity of some queries.  </p>
  
  <p>It is not uncommon to do 10 joins to accomplish any given task in a stored procedure.  I've been told that more then 6 stinks. </p>
  
  <p>Should I keep the table structure as is and provide some materialized views or denormalized "cache" tables.  </p>
  
  <p>Some advice on best-practices or a push in the right direction would help.</p>
  
  <p>Thanks</p>