title: Staging Table Design for Performance
body: <p>I have a typical star pattern in my Azure SQL Data Warehouse.  Data is first dumped into staging tables via Data Factory, then it calls a master procedure that calls other procedures to transform data into the appropriate format and then clear out the staging tables for that chunk of data.  </p>
  
  <p>Should these staging tables have indexes?  Should they have statistics?  I recently upgraded to Gen 2, but don't have auto create statistics turned on.  I worry that statistics will get created but not updated, and so will end up slowing things down more than anything.</p>
  
  <p>For more context, there is a procedure to rebuild indexes and update statistics which is run overnight, once a day.  The data load process is run hourly.</p>