Follow these guidelines to optimize use of the Dataset Attribute Database
feature:
- In a multi-system, shared hard-disk-drive environment, only
enable Dataset Attribute collection on one of the connected systems, ideally
a non-production system. This approach avoids collection of the same data set space
information on multiple systems, and places the work for collection on the
most lightly loaded system.
- Use product-provided queries and workspaces rather than user-created,
as they have been crafted and tuned for maximum performance. User-defined
queries can incur significant overhead if a very large number of data sets
needs to be examined to resolve the predicates.
- User-created situations written against the Dataset Detail table run against
the complete data set database. Do not set a Situation Sampling Interval smaller
than the Dataset Attribute Database collection cycle, because attributes in
the database are not updated more often than that.