title: Why does Redshift not need materialized views or indexes?
body: <p>In the <a href="https://aws.amazon.com/redshift/faqs/" rel="noreferrer">Redshift FAQ</a> under </p>
  
  <blockquote>
    <p>Q: How does the performance of Amazon Redshift compare to most traditional databases for data warehousing and analytics?</p>
  </blockquote>
  
  <p>It says the following:</p>
  
  <blockquote>
    <p>Advanced Compression: Columnar data stores can be compressed much more than row-based data stores because similar data is stored sequentially on disk. Amazon Redshift employs multiple compression techniques and can often achieve significant compression relative to traditional relational data stores. In addition, <strong>Amazon Redshift doesn't require indexes or materialized views and so uses less space than traditional relational database systems</strong>. When loading data into an empty table, Amazon Redshift automatically samples your data and selects the most appropriate compression scheme.</p>
  </blockquote>
  
  <p>Why is this the case?</p>