title: Modeling lookup data
body: <p>Quick question on modeling data for a customer …</p>
  
  <ul>
  <li>Customer stores Store data, about 250 records, maybe 10 properties each.</li>
  <li>Customer stores Department data, about 1,000 record, again, maybe 10 properties each.</li>
  <li>Customer stores Product data, about 2,000,000 records, maybe 20 properties each.</li>
  </ul>
  
  <p>My thoughts for modeling this data, based on how it is accessed is to store Store data and Department data in a <code>lookups</code> collection, partitioned on the <code>object</code> property, in this case, Store of Department.</p>
  
  <p>Store the Product data in a <code>products</code> collection, partitioned on the <code>upc_code</code> property.</p>
  
  <p>Does this make sense? Or is there a better way, specifically with handling small (&lt; 1,000 records) datasets, should I recommend Table Storage for any of this?</p>
  
  <p>Thanks in advance!</p>