Check out this comparison by Chris Eaton and Paul Z on DB2 Blu Acceleration and Microsoft SQL Server columnar indexes. Blu is 3x faster than SQL server, plus SQL server columnar indexes can only be used on read only tables…Not to useful.
I’m finishing up a Chapter on Temporal Tables and found this article helpful. It is by IBM Guru Matthias Nicola.
http://www.ibm.com/developerworks/data/library/techarticle/dm-1204db2temporaldata/
Just a reminder that my article on DB2 LUW Temporal Tables is available from Enterprise Systems Media, at the following link:
Check out this detailed article on Developer Works on new features in DB2 10.5 for LUW for a jumpstart on 10.5.
http://www.ibm.com/developerworks/data/library/techarticle/dm-1304whatsnewdb2105/
With DB2 10.5 WSE you can now use 128 GB of memory per instance. If you have the addl memory then by all means you should upgrade to DB2 10.5.
We had a good turnout at the booth, quite a few new faces to the DB2 LUW space. Our survey indicates that most are still on DB2 9.7 with a few on DB2 10 but most are planning on migrating to DB2 10 in the next 6 – 12 months due to the benefits of such features as jump scan and temporal tables. Stay tuned!
CheckCheck out my article at http://www.enterprisesystemsmedia.com.
Don’t forget to checkout the Big Data track at IDUG in Orlando for the lastest and greatest on Blu Acceleration. Learn how you can accelerate your data with no user indexes required and obtain huge performance improvements through DB2 10.5’s use of the SIMD instruction and columnar data aligned on register boundaries..
Remember, when using the standby as read only, you will want to set the DB2_STANDBY_ISO registry variable to UR as only uncommitted read is allowed on the STANDBY or else you will have to set the isolation level for each application..That’s the view from here…
Good paper on the research leading up to database use of the SIMD instruction for data stored columnwise…