In my last blog I focused on tooling support for the new DB2 BLU Acceleration and rightfully so. BLU Acceleration is a game changer and tooling support makes it even easier to use. I also want to point out there were many enhancements to Data Studio beyond support for BLU Acceleration. A number of requests from the Data Studio user base led to one of these enhancements, checkpoint support in the script editor.
Checkpoint's provide significantly more control over the execution of scripts. It allows the user to, at any point, evaluate the script execution to that point and make decisions on how to proceed. A Data Studio user can set a "checkpoint" at one or more SQL statements. When the script is executing, it will stop before executing any statement with a checkpoint and keep the transaction open. Users may now, in the editor, alter the script, run one or more statements or restart the script from any point. Remember, transactions stays open until committed or the script editor is closed. This can result in locks being held for a long time. Also, remember to commit your work before closing the editor. Any uncommitted statements will be rolled back when the window is closed or Data Studio is shut down.
Let me show you how easy this is to use. First, set your run time options. I recommend selecting "Open a new connection and reuse it to run scripts" and "Stop" on error. This keeps the transaction open and even if there is no checkpoint set, the script will stop at and select any line that generates an error.
To set a checkpoint, right click at the space right before the desired line and select "Add Checkpoint".
Now run the script or use one of the new run options available through the run icon:
Run all statements
Run statements starting from the cursor location
Run selected statements
When Data Studio 4.1 is available, check this feature out. I am sure you will find it valuable.