Published 22 April 2013 - by Iqbal Goralwalla
The IBM BLU Acceleration technology, announced on April 3, 2013, features new innovations from the IBM Research and Development Labs that address the common Big Data issues of size, development time, and response times. This exciting, ground breaking data management innovation for analytic processing is due to be first available in the new DB2 10.5 release for LUW. BLU Acceleration is new technology for analytic queries in DB2 LUW. It introduces columnar capabilities to DB2 databases where table data is stored column-organised rather than row-organised. Its fast, simple to implement and use, low in operating costs, and above all its all embedded in the core DB2 engine. Let me expound on this:
1. Extreme Compression - this addresses the Big Data issue of size.
2. Fast reporting - this addresses the Big Data issue of response times. DB2 with BLU Acceleration comes with:
With all the above, you are on course to getting super-fast response times to your analytic queries. Yes, you longer need to go for that cup of coffee while you wait for your queries to complete!
3. Simplicity - this addresses the Big Data issue of development time and leads to lower operating cost. With BLU Acceleration, the complexity of analytic database design and tuning which involves tedious and mind boggling iterative tasks, disappears! You simply create your BLU tables (existing row-organized tables can easily be converted to BLU column-organized tables), load the data and you are all set to go. Now, hold tight to your chair when you hear this:
- No indexes
- No MDC
- No MQTs
- No Materialized Views
All of the above make it very easy to create a reporting database within a single instance of DB2 from a transactional database to enable operational reporting. There is no ETL process, nor additional software or system required for operational reporting with no required transformations, integration or quality cleansing. Similarly, it becomes quite easy to create and load a BLU in-memory data mart within a single instance of DB2 from an Analytics workload for reporting.
4. Seamless Integration - BLU tables with their columnar data store and non-BLU tables co-exist in the core DB2 engine with the optimiser being aware of both tables. Both types of tables can be accessed using the same SQL and language interfaces, process model, storage, memory and utilities. This follows the trend of pureXML when the XML data store was embedded in the DB2 engine, with XML tables and non- XML tables co-existing in harmony. You decide what type of table you want to use to best suit your application workload.
All the above indeed qualify for ground breaking data management innovation, but the very fact that BLU Acceleration is embedded in the core DB2 engine, known for its reliability and stability seals it for me. Do I sound excited?
Hear Iqbal and George Baklarz talking about DB2 10.5 with BLU Acceleration in our latest podcast series - click here to listen.