title: Database structure and architecture for analytical data to present in UI
body: <p>I need some advice or reassurance...</p>
  
  <p>We are working on an web based application (ASP.NET) on hotel analytics. The Page has different sections that show different charts for specific hotel locations(Total Sales, Room Turnovers etc)for the night before and past history</p>
  
  <p>This data can be run in a nightly job (stored proc) to populate the tables since the data doesnt have to be current. Yesterday data is what is needed not real time. Should each analytic section in the page have the data come from a specific table in the database that is populated by that stored proc (the stored proc will initially get info from multiple tables it needs)? Or is it better for each analytic section have its own table for isolation purposes? For example, all data about Total Sales should be in one table and turnover info on another table.</p>
  
  <p>Im debating and going towards each having its own table since the data is somewhat different. Having all data in one table means there will be a lot of cells with nulls on them. But then again, as new analytics requirement come in, that means adding more tables..</p>
  
  <p>Any ideas?</p>