title: Improve cube processing using an index
body: <p>I have a large fact table (Lets just call it Groupings) that is being used for cube processing. Right now it has approx 850 million rows for 1 year of data and is still being loaded daily, with I think a minimum of 2 million rows per day.</p>
  
  <p>This table has 20 columns, three of these columns are:</p>
  
  <ul>
  <li>GroupCategory varchar (100)</li>
  <li>GroupSubCategory nvarchar(100)</li>
  <li>Date int (which is also the Clustered Index that will be used for    cube partitioning).</li>
  </ul>
  
  <p>I have several measuregroups which has a query below:</p>
  
  <pre><code>Select 
      GroupName
      , GroupCategory
      , ...
      , ...
  from [Groupings] 
  Where 
      GroupCategory = 'GroupCategory_1'
      AND Date &gt;= AnIntDate
      AND Date &lt;  AnIntDate
  </code></pre>
  
  <p>The only difference in the query for the other measuregroups is the <code>'GroupCategory_1'</code>, it could be <code>'GroupCategory_2'</code> or <code>'GroupCategory_3'</code> in other measuregroups.</p>
  
  <p>We need to reduce the cube processing time, and these measuregroups are the bottlenecks. I have already tried making <code>GroupCategory</code> and <code>Date</code> as ClusteredIndex.</p>
  
  <p>I think I am using the right index. I there anything I can check?</p>