title: View vs Table in SQL Server
body: <p><strong>TASK:</strong> for the dashboard purpose, I have a complex select query with lot of joins and sub queries which get the data from multiple tables.</p>
  
  <p><strong>OPTION 1:</strong> I can create a view with that <code>SELECT</code> query and Spotfire can use that view as the data source for its dashboard. </p>
  
  <p><strong>OPTION 2:</strong> I can create a SSIS package by using that <code>SELECT</code> query as a source and I can load the data into a single table <em>ONCE PER DAY</em>. Spotfire can use that single table as a source for its dashboard. </p>
  
  <p><strong>NOTE:</strong> I don't want it REAL TIME. Dashboard can update every night (once per day).</p>
  
  <p><strong>My understanding:</strong> I know that the view is basically a stored <code>SELECT</code> query. If I create a view, every time when a user accesses the Dashboard, it will try to access the view. That means, in the back end view will hit the underlying tables in the database. Instead of this, I can simply have specific table loaded once per a day by SSIS. SO that Dash will touch this table instead of the actual highly transactional tables.</p>
  
  <p>Can you suggest me with an option along with explanation?</p>