What if there were no walls between the DBA and developers?
I'm not really talking about your cubicle walls but those implicit barriers we create when we are so focused on our own thing and work using our own tools. But to develop higher quality applications with more agility, we all need to work together and even cross-pollinate our skills more.
I'm the Team Lead for the Data Studio Developer tooling. Earlier this year, with Data Studio Developer 1.2, we provided tools that help teams break down barriers between developers and DBAs:
- If the developer knew about the queries in their Java application, we told them more about the SQL and the database used by the queries in the Java application
- If the DBA knew about the database, we told them more about where in the Java application the SQL came from.
- DBAs and developers can control the quality and performance of the SQL, and not lose control to a framework.
Flash forward a few months (to now!), and with the announcement of Data Studio Developer 2.1
we have made great strides in two of the most important areas for DBAs and developers:
- We now tell you more about the performance of your SQL and how many times it ran so you can then easily determine the candidates to focus your tuning efforts on. If your product is in the development phase, you can change the SQL in your application. If you are in production, we also give you the ability to replace with a more optimal SQL without changing your application. Automate the performance tests in your regular test buckets and ensure consistent application performance!
- We tell you more (and with greater accuracy) about the SQL in your application, so you can get an answer to a question like "What are all the SELECT statements in my application." Other search criteria can be applied as well.
Most of these new features are available if you are using pureQuery APIs or have an existing JDBC or framework-based applications. And, these features work for both DB2 and IDS servers.
As always, if you use DB2, you can use static SQL to reduce CPU consumption in some cases. With this release, you'll find the experience from developing static SQL applications to deploying them to be significantly improved.
I've written more on developerWorks about What’s new and exciting in IBM Data Studio Developer 2.1.
BTW: I sincerely appreciate the feedback that some of you provided during my IOD sessions where I previewed Data Studio Developer 2.1. Your feedback is really important as we build our new releases.
Watch this space for the announcement of the Data Studio Developer 2.1 download shortly... Then let me know either here or on the Data Studio Forum
what you think of the new release.