title: Database normalization how to normalize approvals/status
body: <p>I'm learning normalization and got some confusion. I'm working on a table.
  Request table.</p>
  
  <ul>
  <li>requestid</li>
  <li>quantity</li>
  <li>requestedby</li>
  <li>requestdate</li>
  <li>approver1</li>
  <li>approver1_additionalinfo</li>
  <li>approval1_dateapproved</li>
  <li>approval1_status(denied/approved)</li>
  <li>approver2</li>
  <li>approver2_additionalinfo(regarding request)</li>
  <li>approval2_dateapproved</li>
  <li>approval2_status(denied/approved)</li>
  </ul>
  
  <p>Per database normalization, fields that are not directly dependent should be separated so i put approval on the separate table.(correct me if i'm wrong)</p>
  
  <p>Table name: Approval1</p>
  
  <ol>
  <li>ApprovalID</li>
  <li>RequestID</li>
  <li>ApproverID</li>
  <li>DateApproved</li>
  <li>AdditionalInfo(type int)</li>
  <li>Status(denied/approved)</li>
  </ol>
  
  <p>Table name: Approval2</p>
  
  <ol>
  <li>ApprovalID</li>
  <li>RequestID</li>
  <li>ApproverID</li>
  <li>DateApproved</li>
  <li>AdditionalInfo(type nvarchar)</li>
  <li>Status(denied/approved)</li>
  </ol>
  
  <p>Based on this design, information regarding request will be on 3 tables and will need more joins to query. It may impact performance.</p>
  
  <p>What is the best approach for this?</p>
  
  <p>Hope someone enlighten me on this. Thanks</p>