As I talked about making the JDBC application run faster in my last entry, a new version of the DSD (Data Studio Developer) is announced. This new release will have a lot more exciting feature apart from what I described in my last entry. Modifying the SQL without changing the source code, Restricting the SQLs to a set to avoid SQL injection, Ehnaced problem determination are some of them. You can find the details of these feature in the below article from sonali
So ready to get going...[Read More]
DB2 Administration and Application Development with Java.
with Tags: purequery X
Have you ever heard/want that your JDBC application run the SQL in static mode ?Have you ever encounter the problem of not able to map the problematic SQL to the source code from where its originated ?Have you ever want to know how many times an SQL get executed by your application ?Or Have you ever want to know how many SQL are there in your application ?
If you face any of these problems and want to know the how you can achieve these goals, try out the new pureQuery support in the IBM data studio product. The client optimizer component actually allow you to capture all the SQLs in you application (even when you don't have the source code of your application) and then allow you to create packages at the db2 sever for those SQLs. Later when your application runs again, you can execute the same SQL in static way. This will not just improve the performance but also give you the benefits of static SQL like different security model, safeguard from SQL injection, control over the access path etc. Capture file also has additional information like source code stack trace for the SQLs and execution count. The tooling in data studio automate the look up for the SQLs in the source code on a click of a button. Below are the links to some article which talk about this product in detail.
the performance numbershttp://www.ibmdatabasemag.com/showArticle.jhtml?articleID=208802229
also look at the video