title: Compound Sort Key vs. Sort Key
body: <p>Let me ask other question about redshift sortkey.
  We're planning to set the sortkey with the columns frequently used in WHERE statement.</p>
  
  <p>So far, the best combination for our system seems to be:
  DISTSTYLE EVEN + COMPOUND SORTKEY + COMPRESSED Column (except for First SortKey column)</p>
  
  <p>Just wondering which can be more better, simple SORTKEY or COMPOUND SORTKEY for our BI tables which can have diversified queries according to users' analysis.  </p>
  
  <p>For example, we set the compound sortkey according to frequency in several queries' WHERE statement as follows. </p>
  
  <pre><code>COMPOUND SORTKEY
  (
  PURCHASE_DATE &lt;-- set as first sort key since it's date column.
  STORE_ID,
  CUTOMER_ID,
  PRODUCT_ID
  )
  </code></pre>
  
  <p>But sometimes it can be queried only 'PRODUCT ID' in actual queries, not with other listed sort keys, nor queried different from COMPOUND KEY order. </p>
  
  <p>In that case, may I ask 'COMPOUND SORTKEY' can be useless or simple SORT KEY can be more effective ...?</p>
  
  <p>I'd be so grateful if you would tell me about your idea and experiences.</p>