Managing the data lifecycle
Howdy! In case you missed it, we just announced a new release of HPU (High Performance Unload) for DB2 for LUW... V4.1. In case you've never looked at our HPU products (for DB2 for z/OS and DB2 for LUW), they can be great productivity enhancers and possibly even save you some resources.
One of the great things about HPU is that it has both a utility-like interface and an SQL interface. The SQL interface is perfect for application developers since they aren't used to invoking utilities. Once invoked, HPU can access the underlying table space or backup / image copy directly, producing multiple data type conversions and unload file formats suitable for most any target data store. When extracting a high volume of data in this way, or by sampling the source, the elapsed time and CPU savings are humongous versus using SQL (or Export or DSNTIAUL).
HPU for DB2 for LUW is also partition-aware, allowing you to unload from multiple partitions with a single execution of HPU into a single output file/pipe or multiple files/pipes. It also provides a re-partitioning capability that unloads and re-partitions the output for new data distribution on the same or different system.
The hot new feature in the 4.1 release for DB2 for LUW adds the ability to migrate data directly (unloading, transferring, and loading) from one database to another without the need for intermediate disk storage. This capability delivers the fastest way to migrate your data. The new release also has other usability improvements and now supports Windows 64-bit platforms.
For more information on HPU, visit http://www.ibm.com/software/data/studio/high-performance-unload/
-- Bryan Smith
Late last month, I asked you DBAs to give me some feedback on our tools for administrators. I'm still looking for more! Thanks to Fred and Rahul both for your comments. Rahul, I believe your issues with DDL generation in Data Studio Developer are being addressed through the forum.
Anyway, since both comments were talking about DDL, it seemed to me like this was the perfect opportunity to talk about Data Studio Administrator, which we just announced on July 8th. Some of you may be familiar with this product under its previous name – DB2 Change Management Expert.
Data Studio Administrator is really designed from the ground up to handle complex database changes. Let’s face it, database changes can be tough. Understanding the dependencies, the authorizations, the effect on applications…. It’s a really big deal to get it right because the consequences of getting it wrong can range from annoying to devastating.The goal of Data Studio Administrator is to make it much easier for you to model the target database, compare two sets of objects to see where they differ, migrate a set of objects to the target, or redefine the target objects to be like the source. Changes automatically roll through all related objects, streamlining the entire change management process.
And, because we all make mistakes, you can automatically undo all changes, if necessary.
There are a lot of other cool things like reporting on the impact of proposed changes to identify dependencies and/or mitigate risk. You can also publish an HTML change report as part of the DDL generation, which looks like this:
So, when you need to do complex, or even simple, schema/DDL changes, the Data Studio Administrator acts as a great process control flow engine to keep you out of hot water. I strongly encourage you to check this webcast on July 23rd by our lead engineer on this project to learn more. If you miss it, there will be a replay available.
Data Studio is all about collaboration, and Data Studio Administrator helps you achieve that with your team. It can integrate input from multiple group members who are participating in the change process. It integrates with Rational Data Architect making it easy to move from logical modeling to physical implementation.
Data Studio Administrator currently supports DB2 for LUW, and we plan to extend it to other DBMS platforms (both IBM and non-IBM) in the future. Stay tuned…
-- Bryan Smith