title: Azure table storage store multiple types
body: <p>What do you recommend in the following scenario:</p>
  
  <p>I have an azure table called Users where as columns are:</p>
  
  <ul>
  <li>PrimaryKey</li>
  <li>RowKey</li>
  <li>Timestamp</li>
  <li>FirstName</li>
  <li>LastName</li>
  <li>Email</li>
  <li>Phone</li>
  </ul>
  
  <p>Then there are different types of tasks for each user let's call them TaskType1 and TaskType2.</p>
  
  <p>Both task types have common columns but then have also type specific columns like this:</p>
  
  <ul>
  <li>PrimaryKey  (this is the same as the Users PrimaryKey to find all tasks belonging to one user)</li>
  <li>RowKey</li>
  <li>Timestamp</li>
  <li>Name</li>
  <li>DueDate</li>
  <li>Description</li>
  <li>Priority</li>
  </ul>
  
  <p>then TaskType1 has additional columns:</p>
  
  <ul>
  <li>EstimationCompletionDate</li>
  <li>IsFeasible</li>
  </ul>
  
  <p>and TaskType2 has it's own specific column:</p>
  
  <ul>
  <li>EstimatedCosts</li>
  </ul>
  
  <p>I know I can store both types in the same table and my question is:</p>
  
  <p>If I use different tables for TaskType1 and TaskType2 what will be the impact in transactions costs? I will guess that if I have 2 tables for each task type and then I will issue a query like: <code>get me all tasks where the task Primarykey is equal to a specific user from Users table PrimaryKey</code> then I will have to run 2 queries for each types (because users can have both tasks type) that means more transactions ... instead if both tasks are in the same table then it will be like 1 query (in the limit of 1000 after pagination transactions) because I will get all the rows where the PartitionKey is the user PartitionKey so the partition is not split that means 1 transaction right?</p>
  
  <p>So did I understood it right that I will have more transactions if I store the tasks in different tables .. ?</p>