Space announcement This space provides the same content as before, but the organization of the home page has changed. The content is now organized based on logical branches instead of legacy book titles. We hope that the new structure will help you quickly find the content that you need.

Working with object sets

This section describes how to work with object sets. Object sets identify the data upon which you want to extract SQL.

Object sets contain naming patterns that identify the objects for which you want to extract SQL. Such objects include:

  • Client IDs (CL)
  • Correlation IDs (CR)
  • Databases (DB)
  • DBRM names (DM)
  • Package names (PG)
  • Plan names (PL)
  • User IDs (US)
  • Tablespace names (TS)
  • Table names (TB)

SQL Performance for DB2 uses these naming patterns combined with source parameters—in which you define such things as the location and source format—to construct a workload from which the product extracts SQL (as shown in the following figure).

Object sets and source parameters

 GUID-3A98C5C6-2050-4E37-ADB2-DBD045020410-low.png

The object set definition is applied to the workload source to extract SQL. The source types include:

  • Apptune archived trace data sets
  • BMC AMI Performance
  • Db2 catalog
  • Db2 Statement cache
  • A DBRM library
  • SQL text data set

Each source type supports different object types. For example, if the source from which you are extracting SQL is the Statement cache, the types of objects for which you can define naming patterns include DBRM names, package names, and user IDs.

Important

You do not need to create object set definitions if your source is a SQL text data set or DBRM source.

This section contains the following topics:


 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*