title: Table design for scheduling calls
body: <p>Say you have a call center that needs to do X amount of calls in a given day. Each customer can be called for Y amount of products that they need to pay. The business would like to assign the calls to the operators at the start of the day and then be able to evaluate daily the results of those calls.</p>
  
  <p>For those reasons, I'm thinking about deviding the structure into two with one table with the customers and another with the products.
  What I am having problem with is deciding the primary key to put in the master scheduling table. Since there will be a good number of records every day, part of me wants to write the data in sequence for each day:</p>
  
  <pre><code>DateOfRecords   date      
  Sequence        int    
  OperatorID      int    
  CustomerID      int
  </code></pre>
  
  <p>Rest of the columns…</p>
  
  <p>With DateOfRecords and sequence being the primary key.</p>
  
  <p>I know that many recommend establishing an integer as a primary key and then index on the other columns. Again, my question comes because of the amount of records to be saved daily given the fact that this will be a historic table.</p>
  
  <p>Any suggestions?</p>