Big Data: BLU Acceleration DB2 Version 10.5 Kepler Considerations

The BLU Acceleration technology is coming out and the new DB2 Version 10.5 Kepler performance improvements are game changing and dramatic especially for Big Data.  I blogged about these features in a more detailed entry (IBM BLU Acceleration – Best Yet for Big Data!). The Columnar data store, 10x compression, in-memory processing, Single Instruction Multiple Data (SIMD) technology, and data skipping are producing almost instantaneous query answers and unbelievable query acceleration for all types of data warehousing and Big Data applications.

Since the response to the new DB2 BLU Acceleration dramatic query performance improvements has been so tremendous, everyone is planning on using DB2 BLU Acceleration and the DB2 Columnar data store for their new Big Data initiatives as soon as it becomes available.  But within every new leap in performance and version of database there are always considerations. With DB2 Version 10.5 Kepler there are three important considerations that need to be put into your plans for leveraging the new DB2 Columnar Big Data capabilities.

DB2 version 10.5 Columnar data store is mainly for read only types of workloads such as Big Data analytics, data warehouse, marketing, auditing and other reporting type applications.  Since it leverages the new technology mentioned earlier, its main mode in this first release is read only.  Insert, update, and delete SQL statements are not allowed yet but are rumored to be coming soon.

The main way of getting all your Big Data into the DB2 Version 10.5 Columnar data store is through the LOAD utility.  The LOAD utility with the REPLACE and INSERT options are the main ingestion processing options.  Again rumor has it that more LOAD utility options and other SQL statements and functions will be coming soon.

IDUG UPDATE:  The DB2 Version 10.5 Columnar data store now handles SQL Inserts, Update and Delete statements.  Also, the LOAD utility options have been improved to include all of the other standard LOAD utility options such as INGEST, IMPORT, INSERT and others.

Since DB2 Columnar is leveraging new types of table definitions and other new database engine access techniques, the Big Data table space table storage needs to be handled through the DB2 LUW Automatic System setting.  In this first release the Big Data DB2 Columnar table requires that its table space has Automatic Storage enabled so that the table space can manage all the extents, compression and data storage attributes.  Your plans should probably use a table space Automatic Storage setting or separate table spaces and buffer pools to get the best performance possible for your new Big Data DB2 Version 10.5 Kepler Columnar tables.

The new BLU Acceleration DB2 Kepler Columnar table data store shows great performance for the beta customers and it will be released very soon so everyone can take advantage of this new exciting technology for all their new Big Data projects.  Follow me on Twitter for IDUG highlights and comments from the conference.


Have you made your plans for IDUG in Orlando this year?  Also make sure to register early and get the IDUG early bird discount. Sign up today!

I look forward to speaking at the IDUG DB2 Tech Conference 2013 North America conference.  The conference will be held in Orlando, Florida on April 29-May 2, 2013.  Get more information at

Also I am involved in the Thursday night IDUG Dine Around.  Sign up at

I will be speaking at the conference presenting Big Data and Analytics Session F07 – “Data Warehouse Designs for Big Data Performance” Wed, May 01, 2013 (02:15 PM – 03:15 PM) in Bonaire 5&6.
Dave Beulke is an internationally recognized DB2 consultant, DB2 trainer and education instructor.  Dave helps his clients improve their strategic direction, dramatically improve DB2 performance and reduce their CPU demand saving millions in their systems, databases and application areas within their mainframe, UNIX and Windows environments.


Leave a Reply

You can use these HTML tags

<a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>