LinkedIn Twitter Facebook
Technology, Design, and Innovation strategist at the Office of the CEO, SAP,  focusing on technology and architecture strategy and strategic operational, product, and management innovation.  Adjunct faculty at Santa Clara University and San Jose State University with the department of computer engineering teaching graduate classes.  Frequent speaker at conferences, special events, Chirag blogs at Cloud Computing.

3 responses to “Challenging Stonebraker’s Assertions On Data Warehouses – Part 1”

  1. Challenging Stonebraker’s Assertions On Data Warehouses – Part 2

    […] out the Part 1 if you haven’t already read it to better understand the context and my disclaimer. This is the […]

  2. Alec Gardner

    Your final comment on Assertion number 3 is why virtualisation of storage *within a single Data Warehouse environment* is so key. This needs to be done wthout the need for manual intervention. Refer assertion 5. It is therefore in fact, very easy and not something that requires more time and energy. Solutions need to be developed at a software layer. Far too many people are falling for hardware ‘innovations’ (this is not new stuff) and assuming it fixes software problems. It never does.

    It becomes important (and more complex) at build time to configure the balance of CPU power and storage in a mixed storage environment but that’s trivial when compared to the benefit of mixed storage over ‘one size (and cost profile) fits all’.