title: SQL Server 2012 - Column Store indexes - Reporting Solution
body: <p>We (Team) are in process of putting Audit Reporting solution for a huge online transactional website.</p>
  
  <p>Our auditing solution is to enable CDC on source table and tracking every change happens on the objects, grab them and push them into Destination table for reporting.</p>
  
  <p>As of now we got one to one table in source - destination.</p>
  
  <p>There will be only inserts in destination and no updates or delete.</p>
  
  <p>So end of the day audit tables will grow large than actual source tables as these keeps history of changes.</p>
  
  <p>My plan is flatten the destination tables to fewer based on subject / module, enable column store indexes and then utilize same for reporting.</p>
  
  <p>Is there any suggestion on the above approach or there is any alternative.</p>