title: Cassandra Performance : Less rows with more columns vs more rows with less columns
body: <p>We are evaluating if we can migrate from SQL SERVER to cassandra for OLAP. As per the internal storage structure we can have wide rows. We almost need to access data by the date. We often need to access data within date range as we have financial data. If we use date as Partition key to support filter by date,we end up having less row with huge number of columns. 
  Will it hamper performance if we have millions of columns for a single row key in future as we process millions of transactions every day. </p>
  
  <p>Do we need to have some changes in the access pattern to have more rows with less number of columns per row.</p>
  
  <p>Need some performance insight to proceed in either direction </p>