It's been less than 5 months since we announced our 1.2 releases of Data Studio, which I blogged about
back in July.
Since then, we have talked to thousands of people, provided demonstrations to hundreds, and visited dozens of customers. People are starting to understand Data Studio and the value of Integrated Data Management better.
With this latest release, announced today, we are really targeting the DBA with enhancements across the portfolio to help DBAs improve application performance, security, manageability, and TCO. In this release, the enhancements are particularly targeting Java applications that access DB2 data, but you'll see we're starting to branch into .NET as well.
The announcements today are for:Data Studio Administrator
2.1, in which we've really focused on both usabilty and functionality. We've done lots of usability testing with DBAs and have provided a more natural approach for doing many tasks, including copy and paste of database changes, flatter traversal of the data source explorer, better sorting and filtering of objects, and new task assistants for utilities, commands and configuration parameters, so you won't have to leave your environment to go out to the command line or control center to perform those tasks.Data Studio Developer
and Data Studio pureQuery Runtime
2.1, which extends the power of pureQuery for developers and DBAs to collaborate together to:
- Eliminate SQL injection risk for Java database applications by giving you the ability to indicate that only SQL that has been captured and approved my be executed.
- Optimize SQL performance by providing developers with the ability to profile the SQL to see immediately how many times a SQL statement is executed, and how long it takes to run (elapsed time), giving developers an easy way to start identifying potential hot spots in the application before coming to the DBA.
- Improve quality of service for OpenJPA and .NET applications. Steve Brodsky blogged about the integration of pureQuery with OpenJPA, which actually was avalable with the 1.2 pureQuery release with WebSphere Application Server v7. For the many many people who ask when can we see the benefits of static SQL with .Net applications, we have taken an initial step in this release by allowing client optimization .NET applications; in other words, the ability to capture dynamically executing SQL and bind them into packages.
Last but not least, DB2 Performance Expert for Linux, UNIX, and Windows 3.2
and the new DB2 Performance Expert Extended Insight Feature
3.2. This is an announcement particularly close to my heart as many of you who have sat in on my talks probably know. Whenever I sit down with DBAs and talk about the problems with diagnosing performance problems in a Java application environment, they always nod their heads in agreement. There is a real pain point here by not having the same diagnostic capabilities for Java as many DBAs are familiar with for COBOL/CICS applications.
If you extend DB2 Performance Expert with the Extended Insight feature (separate PID and separately priced but prereqs DB2 PE), you can enable new end-to-end database monitoring for Java applications for DB2 servers on Linux, UNIX, and Windows. This monitoring capability will really help improve availability of mission-critical database applications by making it much easier to detect performance issues and figure out whether the problem is one in the database or somewhere else in the software stack.
Also, you can set thresholds (your SLAs, so to speak) so you can easily see how the application is performing against those targets. If you haven't read it yet, I encourage you to see the article
that the Germany team who develops this feature wrote. It's a great introduction to this new capability, and it's really just our first step. This whole concept of providing greater insight to DBAs and developers is planned to be rolled out across more databases and more data access environments.
Just a head up. We're not done. We have more announcements coming soon!