Today IBM announced updates to several performance management products, all of which are available individually or as part of the DB2 Advanced Enterprise Server Edition. They include:
We all know that poorly performing applications can lead to lost revenue and customer dissatisfaction. We have made numerous improvements in all these products to make it easier to identify and resolve issues before they can impact your business. There are far too many improvements to list but some notable improvements include:
IBM InfoSphere Optim Performance Manager V5.2
We have added enhancements to better analyze stored procedure performance. Rank stored procedures and drill down to find poorly performing SQL. We have extended reporting now with scheduling, emailing, and retention management. To help you automate actions, we have provided the ability to trigger user defined jobs in response to alerts.
IBM InfoSphere Optim Query Workload Tuner for DB2 Linux, UNIX, Windows V3.2
Once you have identified SQL that could use some help, use Query Workload Tuner to provide suggestions and analyze possible improvements or use Query Workload Tuner to analyze SQL before it ever goes into production. V3.2 has many enhancements to help with "what-if" analysis. Use Query Workload Tuner and virtual indexes to analyze the impact of adding, dropping or changing an index. Use the plan comparator to see the changes to access plans.
IBM InfoSphere Optim pureQuery Runtime for Linux, Unix Windows V3.2
Suppose you have poorly performing SQL from a third party application. pureQuery Runtime can help with that. Use pureQuery to swap out poorly performing SQL. With V3.2, new configuration scripts makes it easier to deploy on WebSphere Application Server and configuration changes can go into effect immediately.
IBM Data Studio V3.2
IBM Data Studio has also been updated. Many enhancements were made to alerts and scheduling in the web console. Users can now define their own alert view preferences. The client was updated to make debugging even simpler and more robust. Debug triggers and PL/SQL anonymous blocks. You can now view global and package variables, associative arrays and array of rows in the debugger. It is also much easier to recompile a routine for debugging. It is almost automatic. Starting with V3.2 the Data Studio administration client will be available via DB2 Express-C
and refreshed as needed. The full client is available via the normal Data Studio download page
. Remember, for the full client, when using the Installation Manager option, only the options selected will be downloaded and installed on your system. If you are using the administration client, try the full client.
Finally, connection management is now easier for many of these products. IBM InfoSphere Optim Performance Manager, Query Workload Tuner, and Data Studio can now obtain and stay synchronized with connection information from the Optim Configuration Manager's database repository.
For more information, check the announcement here
We have been busy working on an update to Data Studio just in time for DB2 10.1 for Linux, Unix and Windows
. This release includes enhancements throughout the product as well as the added support for DB2® V10.1 for Linux, UNIX, and Windows databases which include the following features:
- Adaptive compression for table rows
- Special registers for temporal tables in server profiles
- Time-based data management with temporal tables
- Data management using multi-temperature storage
- Data security with row and column access control (RCAC)
These DB2® V10.1 features are fully supported by Data Studio making it easier for you to take advantage of them.
Other product enhancements include updated syntax checking, additional support for pureScale, improvements to SQL routine support, improved performance information gathering, as well as enhancements to query tuning, shell sharing, and the Data Stuido web console, here are the details:
- We updated the syntax checking in the SQL and XQuery editor for all DB2 for Linux, UNIX, and Windows Command Line Processor (CLP) commands to provide validation of your commands and utilities as well as SQL.
- For pureScale we added support to help verify DB2 Cluster Services Status and Manage DB2 Cluster Services Configuration to further assist in the use of pureScale in your enterprise.
- We have made the following improvements around SQL routine support:
- You can now use the routine editor to create, edit, deploy, run and debug routines directly from the Data Source Explorer without having to create projects, simplifying the task of routine development when there is no other need for a development project.
- Likewise, you can re-compile a routine directly from the Data Source Explorer to enable/disable debugging.
- You can now create unit routine test cases with saved parameters and pre/post SQLs and then compare the current results with a saved base line result. This helps catch regressions when editing routines.
- To make it easier to tune your SQL before deployment, there is now an improved user interface for profiling DB2 LUW routines and to simplify integration, you can invoke InfoSphere Optim Query Workload Tuner from the profiling view.
- You can now use the Configuration Checker to verify that all essential server components are in place for routine development on DB2 Z.
- We made it easier to gather database performance information for stored procedures in DB2 for Linux, UNIX, and Windows databases.
The query tuning features in Data Studio have been enhanced to include the following:
- We added a Start Tuning wizard to the Task Launcher for a better up and running experience
- Our access plan graphs can now display three new nodes:
- Show the rebalancing of rows between SMP subagents with REBAL
- Show multi-distinct processing with MGSTRM
- Show a zigzag join with ZZJOIN
In addition to the Data Studio query tuning enhancements, the client for InfoSphere Optim Query Workload Tuner is now part of the Data Studio v3.1.1 product. After you install Data Studio v3.1.1, all that you need is a license to enable InfoSphere Optim Query Workload Tuner, simplifying the install process for those of you who use both Data Studio and InfoSphere Optim Query Workload Tuner.
On top of all the new functionality, the Data Studio v3.1.1 clients are now built off of Eclipse 3.6, which means the Data Studio full client is now compatible (for shell-sharing) with newer Eclipse based offerings such as the latest IBM Rational Application Developer and Rational Developer for System z.
For the Data Studio web console, we have included the following enhancements:
- New alerts so that you can configure for the following:
- High availability disaster recovery (HADR) databases
- DB2 pureScale instance status
- When the DB2 pureScale cluster facility is not found
- For DB2 V10.1 for Linux, UNIX, and Windows databases, we also added the following enhancements:
- Your storage group information is provided in alerts both under the 'Storage' category as well as on the 'Current Table Spaces' dashboard.
- You can create and manage user-defined alert types using custom scripts so you are no longer limited to the out-of-box alerts.
- You can import existing tasks from the DB2 Task Center into the Job Manager to ease the move from the DB2 Task Center to the Job Manager in Data Studio.
- You have more control over your jobs as we have added the ability to cancel a job that has started and specify a timeout period for your jobs.
Visit the Data Studio product page
and download from developerWorks
. Data Studio is bundled with a number of IBM data servers such as DB2 for Linux, Unix and Windows, DB2 Connect and IBM Informix. For a good overview, check out the "Getting started with IBM Data Studio for DB2
I've been a development manager on database administration capabilities for Data Studio for many years, and recently took over as product manager, as well. I am very excited about our new Data Studio 3.1 release. It not only includes enhancements to the previous release of Data Studio, but, more importantly, combines the feature set of Optim Database Administrator and Optim Development Studio with Data Studio and Data Studio Health Monitor to create one comprehensive product for application development and database administration, all available at no charge! Data Studio can be found as a download from developerWorks
and soon will be bundled with a number of IBM data servers such as DB2 for Linux, Unix and Windows, DB2 Connect and IBM Informix.
Data Studio 3.1 now consists of three components:
Data Studio administration client: Reduced footprint client for administration and non-Java based development. (You may remember we referred to this previously as the stand-alone package)
Data Studio full client: Full-feature client that can shell-share with other Eclipse-based products (This was previously called the integrated development environment package) .
Data Studio web console: health monitoring and new job scheduling capability (this was formerly known as Data Studio Health Monitor)
In addition to the consolidation, we've enhanced the following areas:
The object management feature has been completely overhauled. The new UI provides for in place editing of objects and eliminates the need for a separate editor. Complex object management for Optim Database Administrator for DB2 for Linux, Unix and Windows has been incorporated into the new object management for Data Studio 3.1.
There are a number of enhancements related to navigating, monitoring and managing a DB2 pureScale environment.
There are numerous enhancements to the query editor. They include version specific validation, execution control and special register support.
You can now change the user name and password on any or all connections with one action. The Data Studio web console also provides a central place to define database connections that can be imported by the Data Studio full or admin clients.
Compare and Sync
There are enhancements to reporting and visualizing changes.
DB2 for z/OS
We added support for temporal tables and query tuning now includes set/update profile support for runstats and table data sampling
Scripts may be scheduled as jdbc or clp scripts for DB2 for Linux, Unix and Windows and jdbc scripts for DB2 for z/OS.
You can find current Data Studio product information here
. Check out and post questions, comments, or requests on our forum
or visit our information center
and information roadmap.
P.S: Today we also announced the following:InfoSphere Data Architect 7.6 InfoSphere Optim pureQuery Runtime z/OS 3.1InfoSphere Optim pureQuery Runtime LUW 3.1InfoSphere Optim Query Workload Tuner LUW 3.1 InfoSphere Optim Query Workload Tuner z/OS 3.1
We released several fix packs on June 30th and a modification release on July 1. There are a few new features and platform support worth taking time to highlight.
Optim Performance Manager – Optim Performance Manager 4.1.1 is now available. We put a lot of focus on up-and-running improvements in this release. This includes embedding a lightweight web container to simplify installation, configuration, and security, simplifying our port infrastructure for Extended Insight support, improving the out-of-the-box monitoring templates based on customer experience and more. We have added pureScale-specific monitoring enhancements including pureScale monitoring templates, group buffer pool hit ratios, cluster facility lock wait time, escalations, timeouts, etc. We provided more flexibility for monitoring large DPF environments by separating collection intervals for bufferpool versus tablespace and table statistics, which provides more comprehensive information at a lower cost. We have also included DB2 Enterprise Server Edition 9.7 for use with Optim Performance Manager. For the complete list of features and more information, see the IBM Optim Performance Manager 4.1.1 release notes.
Optim Development Studio – Optim Development Studio 18.104.22.168 now also officially supports deployment on Citrix (I know several organizations that went ahead and deployed before our formal support was announced). It also includes two very cool items:
- Integration with Optim Performance Manager – Now you can pull performance metrics into Optim Development Studio to assist in determining which SQL statements need a little more tuning and whether your tuning efforts are paying off. This integration requires Optim Performance Manager Extended Edition with Extended Insight monitoring configured.
- Support for Sybase - You can connect to a Sybase database and browse catalogs, manage objects, create and run SQL scripts, and create, deploy, run, and debug stored procedures. Plus you can use the ANTs Software product IBM® DB2 SSacSA to connect to a DB2 for Linux, UNIX, and Windows database as a Sybase database.
Remember, Optim Development Studio is available on Passport Advantage to most DB2 and Informix customers as part of their DB2 for Linux, UNIX, and Windows, DB2 Connect, or Informix investment. Find it in the Linux or Windows eAssemblies. See IBM Optim Development Studio Version 22.214.171.124 Release Notes
for a more information and download updates from Fix Central
Optim Database Administrator - Optim Database Administrator 126.96.36.199 also adds official support for Citrix deployment. It also sports a new table data editor for DB2 for LUW and z/OS databases and closed a couple gaps in the dependency analysis space for packages and procedures. It also includes catalog filtering improvements tailored to very large databases. Optim Database Administrator is available to DB2 for Linux, UNIX, and Windows customers as part of their DB2 9.7 Linux or Windows eAssembles on Passport Advantage. See IBM Optim Database Administrator Version 188.8.131.52 Release Notes for more information and download updates from Fix Central.
Data Studio – Data Studio 184.108.40.206, both stand-alone and IDE, inherit the Optim Database Administrator Citrix, table data editor, dependency analysis, and catalog filtering enhancements. In addition, this release includes some enhancements specifically for DB2 for z/OS, notably use of TABLESAMPLE keyword on statistics recommendations and catalog navigation performance improvements. For more information, see the IBM Data Studio Version 220.127.116.11 Release Notes. Download updates from Fix Central or a fresh install at developerWorks.
Check them out and post questions, comments, or requests here or on our forums
We released several fixpacks on April 19th that I want to call your attention to. Not only do they provide defect fixes, but also some cool new function.Data Studio Health Monitor
- This fixpack adds support for health monitoring for DB2 for z/OS as well as alert notification support. Customers that we previewed the function with really liked the easy setup and the ability to share it with teams members in development and other operations staff. It monitors and alerts application blocking conditions like database down or log full plus users can view system log messages and see what application and utilities are running. Data Studio Health Monitoring is available at no charge and support DB2 for z/OS and DB2 for Linux, UNIX, and Windows databases. Check it out now! For more information, see the IBM Data Studio Health Monitor Version 18.104.22.168 Release Notes
and product overview
pages. You can download Data Studio Health Monitor V22.214.171.124 for an upgrade from version 2.2.1 or for a fresh install at IBM software downloads
.Optim Query Tuner
- Query Tuner users will definitely want to pick this up! This fixpack for Optim Query Tuner offerings provides a new Access Plan Explorer. Many customers who have very complex SQL wanted a textual access plan navigation method in additional to the visual explain. This new tool displays access plans as tables or hierarchical trees. There are also additional usability and SQL capture enhancements. See What's New in Optim Query Tuner
and the Release Notes
pages.InfoSphere Data Architect
- This is a standard fixpack with defect fixes. For more information, see the IBM InfoSphere Data Architect Version 126.96.36.199 Release Notes
and product overview
pages. View the download document
to learn how to download InfoSphere Data Architect V188.8.131.52 to upgrade from version 7.5.3.
Let us know how you like these enhancements :-)
I talk to many, many people about pureQuery and the benefits it can bring to performance, security, and problem determination of database applications. A key part of being able to deliver these enhancements to the wide variety of existing Java applications is the ability to layer pureQuery optimization onto existing applications without making changes to the application code. This process is called client optimization.
We have some enterprise customers now reaping the benefits of client optimization leading to this delivery which helps further improve security, manageability, and scalability to support complex enterprise environments. The main result of these requirements is delivery of a shared repository that can be used to securely store pureQuery artifacts. Not only does this provide added security, it provides the DBA with centralized control of the client optimization process. In other words, after the initial pureQuery Runtime setup within the application server by the administrator, you, the DBA, can modify the application’s pureQuery Runtime environment configuration without requiring further changes to the application server.
In addition, the centralized repository makes it possible to do continuous capturing, providing a step toward the vision of a more automated capture, configure, and bind process.
Another enhancement based on customer requests is the ability to group SQL into packages based on string tokens or special register values to streamline and simplify package management. An example of where this can be useful is if you are currently using special registers to set the schema qualifier during dynamic execution. Now you can package up the appropriate SQL statements into separate packages (one per schema for example) and do the same thing statically using the QUALIFIER BIND option.
To help make sense of these enhancements, the product documentation for client optimization has been updated with scenario-based guidance on running, deploying, managing, and troubleshooting the client optimization process.
If you are interested in hearing more about the capabilities in this release from product experts, I invite you to join us on June 24th for the Virtual Tech Briefing entitled pureQuery Deep Dive Part 3: Client optimization administration. My colleagues Patrick Titzler and Chris Farrar, who some of you may remember from the first pureQuery deep dive tech briefing, will provide and overview of the new capabilities, how it fits into the overall direction we’re going, and will be available to answer questions. Patrick is planning also to do some demos of the tooling support for these features delivered in the Optim Development Studio Fix Pack 3.
- Download document that links to Optim Development Studio 2.2 Fix Pack 3
- Download document that links to pureQuery Runtime for Linux, UNIX, and Windows 2.2 Fix Pack 3. The APAR number for the pureQuery Runtime for z/OS delivery is PM15915. The PTF is UK57844
- pureQuery client optimization topic in the Integrated Data Management Information Center
- Register for the June 24th Virtual Tech Briefing on the enhancements delivered in this release
We recently uploaded Fix Packs for many of our products. The major theme for these Fix Packs is support for Windows 7. Here are the product Fix Packs that include the Windows 7 support with links to the appropriate download documentation.
You may notice that High Performance Unload is not in that list. I will post again when that fix pack is ready.
Remember, you can find help from volunteers and other users at discussion forums that are available for all of these products. See the Integrated Data Management community space for links to all discussion forums on developerWorks.
A quick note to let you know that I recently updated my article on packaging for the Optim solutions for database development, administration, and performance management (sometimes known as ‘heritage Data Studio’). The major changes were to include functional changes introduced with the Fix Packs that I blogged about earlier, to include the bundled solutions we offer, and to update links to announcement letters, relevant blog entries and more.
The intention of this article is to answer typical questions I get about feature/functionality, including supported databases, across the portfolio. I hope this helps.
Hi, all. I am a developer on our Optim Query Tuner products. A new feature called ‘Compare Access Plan’ was shipped in Optim Query Tuner (for DB2 for z/OS) and Query Workload Tuner V2.2 fix pack 1
that allow DB2 for z/OS DBAs to compare the access path cost of SQL statements in packages between the latest two EXPLAIN versions. The tool generates a HTML report that provides high level package cost and individual package details.
In this blog, I’ll describe how to launch the feature, and then I’ll describe some common scenarios. Launching the Access Plan Comparison
First you must be connected to a DB2 for z/OS server. You can then invoke this feature by going to Data Source Explorer->Query Tuner->Compare Access Plans
The following input screen is displayed:
Each of the options circled above is useful for different scenarios, which I’ll describe here.Option: Compare two collections that contain the same packages
Use this option in scenarios such as:
- Identifying packages whose performance can be impacted following DB2 migration from one release to another. It can help you identify packages that can benefit from REBIND after migration and packages that should not be rebound
- After running RUNSTATS to identify packages whose performance can be impacted if a REBIND is performed.
Let’s look at the first scenario in more detail - version to version migration. In DB2 for z/OS environment, after migration you have two options for running application programs that contains embedded SQL statements:
- REBIND – Rebind the existing packages to make use of new features that are introduced in the newer version. However, the rebind may alter (positively or negatively) the access plan of SQL statements in the underlying packages.
- Do nothing – Continue to operate with the packages that were bound in the earlier DB2 version. Thus there are no changes in the access plan of the SQL statements in the underlying packages. The flip side is that some of the SQL statements that could benefit from changes in the newer DB2 version would still operate in the old way.
Assume that you want to determine if you need to rebind the selected collections (group of packages) to exploit new features available in the new version of DB2 for better performance. You would need to do the following:
- Before the migration, bind any packages that are going to be analyzed with EXPLAIN(YES).
- After the migration, bind the packages to a new collection with EXPLAIN(YES) to insure that the current packages are not overlaid and are available for execution. The packages must be exactly the same in the before and after migration collections. The underlying application programs must not be changed in any way or rebuilt. Also be sure that the EXPLAIN output for the bind points to the same set of EXPLAIN tables. In either case, the access plan comparison report will show an error if you don’t do this correctly.
- From Optim Query Tuner, in the input screen shown above, you specify the sets of collections to be compared by entering the name of the first collection in the Source Collection Name field. For example, in a migration scenario, the source collection might be the name of the collection prior to the migration and the target collection might be the name of the collection following the migration. You can also use filtering to narrow down to a subset of packages.
- Click Add. See the screen-shot below for an example (you can repeat the above steps to add additional collections):
- Click Generate Report to get the comparison report. Query Tuner will look into the catalog tables and EXPLAIN output to compare the access plan of all the operative and valid SQL statements in the underlying packages pre and post migration of the selected collection(s) and then generate an HTML comparison report.
The HTML report is self-descriptive. It displays result in two sections:Summary Table shown below:
Lists out all the compared packages in decreasing order of the performance degradation. Thus the package whose performance has degraded the most is shown at the top. The package cost is determined by aggregating the cost of individual SQL statements within the package. TOTAL_COST is used as a parameter for computing performance degradation. However TOTAL_COST information was added in the explain table only in DB2 z/OS v8 new function mode. For releases that don’t have this information, the PROCMS value is used to determine the performance degradation. For easy navigation, your can click on the package name to navigate to the section where the package details are listed. Package Table shown below:
Lists out all the SQL statements within a package in the decreasing order of the performance degradation. The same parameter that was used for determining package degradation is used for computing individual SQL degradation also.
Use this report to determine whether or not the performance of the SQL statements in the target collection has degraded or whether any packages have errors. Packages that have errors are highlighted in red, indicating one of the following reasons:
- The collection name is invalid or no qualifying packages were found.
- The package content was different between the two collections.
- A package appears in only one of the collections.
- The explain entries are missing for a package in one or both of the collections.
You can save the report by clicking Save Report
. Firefox users can use the save and print feature to save the report.
What to do next
You would either rebind the package/s to the original collection to make them live, or begin analysis of those statements that have been identified as having degradation in performance and not rebind them until you have resolved any performance issues. You can use Optim Query Tuner to analyze the SQL statements that have problems and to receive specific advice about the problem queries.
Option: Compare two different versions of the same collection
Use this option for those cases when you rebind packages regularly and want to gain an understanding of the changes in the access plan before and after the rebind. As with the previous scenario, bind any packages that are going to be analyzed with EXPLAIN(YES), before the rebind. Then rebind packages to the original collection with EXPLAIN(YES) to insure that the current packages are overlaid and are available for execution. The packages pre- and post-rebinds must be exactly the same. The underlying application programs must not be rebuilt or changed in any way.
Now, in the input screen you will specify the name for the collection that contains the packages to be analyzed in the Collection Name
field as shown here:
Click Generate Report
to get the comparison report. Query Tuner will look into the catalog tables and EXPLAIN output to compare the access plan of all the operative and valid SQL statements in the underlying packages pre and post rebind of the selected collection(s) and then generate a comparison report. From the generated HTML report you can determine whether or not the later version of the collection has degraded performance.
I hope you find this new feature useful. Let us know what you think. You can also ask questions and discuss with other users on the Optim Query Tuning Solutions discussion forum
The Optim Development Studio 2.2 Fix Pack 1
was made available on December 11. Although a fix pack, the focus is on customer requirements, so there are many "new" features focused on pureQuery development. These features are suggestions from our customers, based on their extensive usage of pureQuery on large scale projects, to improve developer productivity. We hope you will benefit from these while building pureQuery applications. To see what pureQuery brings to your organization, read my earlier article
Here are some of the highlights of the fix pack.Speedy pureQuery application iterative testing
- As part of pureQuery development, you are always changing your SQL in the annotated style interfaces. You now have the ability to generate JUnits for those interfaces and speed up testing. Simply right click on the annotated interface from the package explorer and select Generate JUnit
from the menu. Improved SQL support in Java database applications
Improved developer and DBA handshake
- Bridging the gap between Java and SQL has been one of the key benefits of pureQuery since the first release. This feature has been improved to allow live validation of SQL against the database, if you have a live connection available. This is a sure shot way to ensure SQL is accurately validated, and you may want to always set this flag if you have a live database connection.
You can set this flag (called “Validate SQL problems against live database”) from Window->Preferences->pureQuery, or from the project properties.
- SQL merge statements can now be auto-generated when pureQuery code is generated from one or more tables and at least one primary key exists on the table(s). Simply check the boxes for SQL merge statements in the pureQuery code generation wizard (by default, they are checked).
We are providing yet another step towards seamless integration between the developer and DBA roles. When using Optim Development Studio to bind SQL into static SQL packages, you can now generate .bat or .sh files which can be shared with the DBA. The DBA can use that as a starting point to customize the bind calls, or use them as is.Improved usability for tuning queries in ODS using Optim Query Tuner
You can generate reports that suggest how to tune SQL statements for better performance, when Optim Query Tuner
is installed in a shell shared environment with Optim Development Studio. Simply right click on an SQL statement from your pureQuery application or from the SQL Outline, and select Generate Query Tuner report
from the pureQuery menu.Improved support for application development when using the pureQuery API
Applications often need to access SQL from multiple schemas within the same project. This is now possible when building pureQuery annotated style applications. You can specify different schemas (to quality unqualified tables/ views) or paths (to qualify unqualified procedures/ functions) for each annotated interface in a pureQuery application, and these values will be used for SQL development/editing within your interfaces. To enable this, right click on the annotated style interface and provide values using the Connection Settings.Improved support to use existing beans when using pureQuery API
If you use customized row handlers in your pureQuery applications, you can now get a head start in building these by customizing the ones generated by pureQuery. Using this new feature, you can externalize row handlers from an interface into separate files, and enable re-use. To see this feature in action, right click on the annotated style interface from the Package Explorer and select Create Handler Classes
from the pureQuery menu.
In addition to the above Optim Development Studio features, there are numerous enhancements in the Optim pureQuery Runtime Fix Pack
- Usability improvements in the static binder that allow you to specify package level bind options and allows more control over packages to bind from various artifacts
- Improved exception handling to get access to underlying sqlstate and sqlcode easily
- There are also improvements in serviceability and literal substitution features
We hope you will download the fix packs and try some of these enhancements.
As always, let us know what features you would like to see and please keep the feedback coming! Feel free to submit questions using the Optim Development Studio and pureQuery Runtime forum
With the holidays just around the corner, this is the right time to add to the spirit by announcing the new release of Data Studio
184.108.40.206 (the complimentary tooling for DB2 and IDS). Along with improved quality, following are the two significant functionalities we added:
- Administration of DB2 pureScale: If you aren't already aware, DB2's new version provides continuous availability through the use of highly reliable IBM PowerHA technology on IBM Power systems and a cluster- based shared disk architecture. DB2 pureScale provides practically unlimited capacity for any transactional workload. Thanks to a proven, scalable architecture, you can grow your application to meet the most demanding business requirements. Using Data Studio, you can do the following administrative tasks on DB2 pureScale
- Cluster Members: Start, Stop, Configure, Quiesce, Unquiesce
- PowerHA pureScale Server (CF): Start, Stop, Configure
- Basic single query tuning features: The following features have been incorporated from the deprecated Optimization Service Center for DB2 for z/OS:
- Capture queries from all data sources that Optimization Service Center for DB2 for z/OS supports and from XML files that are exported from DB2 Query Monitor for z/OS.
- View formatted queries.
- View access plan graphs.
- Capture information about the data server that queries run against, a feature which corresponds to Service SQL in Optimization Service Center for DB2 for z/OS
- Generate reports on the performance of queries.
- Run the Query Statistics Advisor to analyze the statistics that are available for the data that a query accesses, check for inaccurate, outdated, or conflicting statistics, and look for additional statistics that you might capture to improve how the data server processes the query.
Note that even if the above features have a legacy in the Optimization Service Center for DB2 for z/OS, you also get the same functionality for DB2 for Linux, UNIX, and Windows in Data Studio. For integration with Optim Development Studio
or for more advisors, such as Query Advisor, Access Path Advisor and Index Advisor, you need Optim Query Tuner
The above new features are only available from the stand-alone package of Data Studio, which is being refreshed. Hereis a link to the download document
that includes links to both the Data Studio stand-alone refresh and IDE Fix Pack.
Or, if you want to go ahead and download Data Studio stand-alone right now, here is a direct link
. And don’t forget the new free e-book, Getting Started with Data Studio for DB2, which you can download here
We have a lot of exciting things planned for 2010. So stay tuned and happy holidays!!
Updated December 15 to correct a typo.
I am the software architect for InfoSphere Data Architect
, and I wanted to spend a few minutes telling you what we’ve been cooking at the Lab over the past few months to deliver Fix Pack 1
for IDA 7.5.2, which was made available on December 11.
In this Fix Pack, we’ve added new features and improvement in a number of key areas, which I’ll highlight here. Diagramming improvements:
We are excited to have started incorporating the ILOG diagramming technology into InfoSphere Data Architect to provide an enhanced diagram layout. The new diagramming capability will offer choices of layouts as well the option to specify the spacing of objects, all very important steps towards offering greater control and flexibility of visualization.Import DB2 physical objects from other tools:
For years, InfoSphere Data Architect has offered the capability to import models from other tools. Significant in Fix Pack 1, we have provided unique capability to help import DB2-specific properties for physical database objects, such as index and storage, faithfully into IDA from other tools like CA ERwin and CA Gen. Whereas generic export/import capabilities may cause you to lose this information, this enhancement in IDA will enable you to preserve your existing data design efforts. Import from COBOL source files and copybooks:
Although this capability was on a temporary leave, our z/OS friends will be happy to know that this capability is back in with this Fix Pack. This "legacy data" often contains critical information, so they need to be included in the data modeling process. Filtering improvements for productivity and performance:
It is now possible to have a couple different approaches of specifying filters for model comparison and synchronization: you can specify filter options at the workspace level to streamline and improve overall comparison performance, and you can specify filter options at individual comparison invocation to improve ease of use of the comparison editor. Integration with InfoSphere Discovery (forrmerly Exeros):
Those familiar with our history and approach know that we have a strong focus in building linkage points across IBM products. This ability to easily share and collaborate the metadata is crucial to the acceleration of projects. In IDA 220.127.116.11, we continue this focus with the introduction of the integration with InfoSphere Discovery
. With this new capability, you can import the discovered metadata from InfoSphere Discovery directly into InfoSphere Data Architect and share and use it in a wide range of scenarios including the Optim Data Archiving
and Data Privacy
solutions, as well as InfoSphere Foundation Tools
For more details on the contents of this Fix Pack, be sure to read the Release Notes
Let me close by saying that the InfoSphere Data Architect team loves getting your input so please keep them coming. Feel free to post your comments and questions on the IDA forum
. We are excited about what we are going to do in 2010!
I was at the Lab in San Jose this week doing some planning and meeting with Business Partners. The folks here say the cold is pretty unreasonable, but I’m heading back to the upper Midwest, so I don’t think they have much room to complain.
Anyway, today we are shipping a set of Fix Packs and refreshes to our portfolio of database admin and tuning products. Some individual product architects will be blogging in more detail about what is in the Fix Packs, but I wanted to give you a head start on downloading by giving you a summary list of all the download documents that tell you how to find what you need. Reminder:
two product releases that Holly Hayes blogged
about in November also are electronically available today. Links to their download documents are here:
Have a great holiday.
The fix packs for products in the Data Studio family 2.1 have arrived!
The fix packs includes enhancements and fixes to the Version 2.1 release of IBM Data Studio Developer, IBM Data Studio Administrator, IBM Data Studio pureQuery Runtime and of InfoSphere Data Architect 7.5.1. These fix packs are intended to fix problems you may have experienced in the 2.1 release. For additional information or detail on included fixes please check out these links.Data Studio Administrator Fix Pack 1 InfoSphere Data Architect Fix Pack 1Data Studio Developer Fix Pack 1
For those who already have these products installed on Windows, you will use IBM Installation Manager to apply the fix pack:
- Go to the link to download the compress file for Fix Pack 1 and then extract it to a temporary directory. For example, C:\temp
- Start the IBM Installation Manager by going to Start > All Programs > IBM Installation Manager > IBM installation Manager
- In the IBM Installation Manager, click File > Preferences... this will launch Preferences wizard. What you want to do here is click "Add Repository..." and then you can put the path for fix pack 1. For example, C:\temp. Click OK after you have entered the path and click Apply on the Preferences page and OK.
- Back in the IBM Installation Manager start page, click Update Packages.
- Select IBM Data Studio (for Data Studio Administrator or Developer) or IBM Software Delivery Platform (for InfoSphere Data Architect) as the package you want to update and click Next.
- On the licensing page, read the license agreement and select "I accept the terms in the license agreement" and click Next.
- On the summary page, verify the installation information and click Update. This will begin the installation of the fix pack on your system.
- When the installation is complete you can click Finish, and close IBM Installation Manager.
For those who don't have the products installed, go ahead and download the trial versions of the products from the following links:Data Studio Developer Data Studio Administrator InfoSphere Data Architect
(By they way, you can find all these links together on the Data Studio Community Space
- Unzip the Data Studio package you just downloaded and click setup.exe. This will launch/install IBM Installation Manager.
- When prompted to select packages to install, click Check for Other Versions and Extensions. This will show you both the newest IBM Installation Manager, plus the fix pack!
Now you are ready to go!
We also have fix packs for DB2 Performance Expert and DB2 Performance Expert Insight Feature:DB2 Performance Expert Version 3.2 Fix Pack 1DB2 Performance Expert Extended Insight Feature Version 3.2 Fix Pack 1
-- Tina Chen