DB2 10 for LUW Tools: Love and Hate

First, I want to thank everyone for their emails regarding the Optim products that I wrote about last week.  The reasons the comment sections on the blog are shut down is because I can’t keep up with the all the spammers while I am consulting or teaching.  So please keep the emails comments coming I appreciate everyone’s experiences and points of view.  This week’s blog is about all these comments.

If you’ve missed any of the previous weeks’ blogs on DB2 10 for Linus, UNIX and Windows, they are available for you to read by putting “DB2 10 for LUW” into the blog search box or by using the blog navigational tools.

Some people thought I was too easy on the Optim tools.  Let me say that I have a love-hate relationship with all the tool vendors.  Being in many companies’ beta programs over the years to review many products has been interesting. Some had great new functions and some missed expectations.  While the Optim tools do have a lot of functionality, any vendor may have problems.  Especially with a new DB2 10 for LUW, the tools won’t do everything with the first release.  My many clients have different specialized situations and I have seen vendor tools work or not work in two different shops even though they were performing the same type of function. There is no substitute for testing vendor tool functionality in your shop with your data with your specialized requirements.  DB2 10 for LUW has many great features for the vendors to leverage and real life testing is the only thing that proves a tool’s true return on investment within your company. 

Next, the majority of the comments and questions were asking whether the Optim tools would do that function or fix this problem.  The real answer is that it really depends on the tool, release level and your shop’s unique data and configuration.  I always test all the tools through an excruciating amount of situations and tests to verify any sales person telling that the functionality works.  The truth is only realized in your testing in your specialized environment; assume that the sales person is giving you the information as he or she knows it, but no one knows whether it will be a success for your shop’s unique criteria and situation. 

Data management is hard and there are no silver bullets to slay the problems.  The data management problems are only getting bigger, cloudier and more complex.  Database designs that have been stretched to their limits, applications that have had years of neglect, and systems that now must scale for mobile phone usage are only a few of the types of complex issues IT faces.  DB2 10 for LUW tools and features will help, but they don’t address core data management issues. 

Finally, working with the many systems, applications and different tools over the years has left me jaded.  I try to be neutral when I talk about all the products because I have seen great tools over the years become bloated pieces of software trying to do too many functions.  I continue to be hopeful for all the new releases of any of the products and especially look forward to seeing all the new DB2 10 for LUW tools at the upcoming IDUG conference in Denver.  Unfortunately, history has taught me that a DB2 CLI (command line interface) or TSO SPUFI SQL or a monitor with no overhead that accurately collects and reports trace records are the best tools to use.  These interfaces don’t usually crash, don’t have a confusing GUI, require software fixes, act consistently across all my consulting and educational clients and are consistent all the way through to this new version of DB2 10 for LUW.  Vendor tools help with all types of automation and problems but they are never a substitute for good data management best practices, good database designs and full research of the application development of the correct functionality for the life of the system. 

Reliability, availability and scalability (RAS) are designed into database and developed through good application requirements and coding.  The many Java framework failures, application coding problems and object anomalies along with new big data and cheap cloud processors are leading us all to many new data management challenges.  The key to leveraging the new DB2 10 for LUW features will significantly improve your systems RAS.  Tools always help but can never fix a poor design or bad application framework or inefficient coding. 

So check out all the DB2 10 for LUW tools, especially the ones from vendors other than IBM.  The only way these vendors stay in business is because they provide needed functionality and solutions.  Keep the DB2 LUW tools markets going by telling and buying from all the vendors at IDUG conference in Denver.


I will be providing my first TWITTER comments during this year’s IDUG conference in May.  I will highlight the various conference activities, presentations, vendors and IBM announcements.  Please sign up to follow me on TWITTER (@DBeulke) and get all the latest IDUG DB2 related news from the conference.


Set up your agenda within IDUG today!

If you are already signed up for the IDUG conference, don’t forget to make your conference presentation agenda.  Make sure to include my session E09 – Java DB2 Developer Performance Best Practices Thursday, May 17, 2012 8:30 AM – 09:30.  The conference will be held in Denver, Colorado on May 14-18, 2012.  Sign up today at www.idug.org.


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>