Skip Headers

Oracle Discoverer Administrator Administration Guide 10g (9.0.4) Part Number B10270-01 |
Home | Contents | Index

## Summary Wizard (ASM): Change default settings dialog: Query Usage tab

Use this tab to select which queries are considered for summary recommendation. For example, to include only queries run a specific time when Discoverer Plus users are working.

For more information, see:

"Managing summary folders"

#### Include

Use this drop down list to define which queries are considered for ASM.

#### All queries

Use this option to consider recommendations for summaries based upon all queries previously run.

#### Queries run since last execution

Use this option to consider recommendations for summaries based upon those queries run since the last execution of ASM.

#### Specific queries

Use this option to consider queries run at particular times, specified below.

- Which have been run in the last x days

- Which have been executed more than x times per minute/day/week/month/year

- Where elapsed time is greater than x seconds

#### Move the slider to the position which best reflects the nature of your users queries

Use this slider bar to determine whether during analysis the constructed summary data favors predetermined (performance) or ad hoc (coverage) queries.

#### Predetermined

Use this setting to optimize the summaries maintained by ASM to reflect historical queries. In other words, the summaries will give great performance improvements where queries stay much the same over time.

For example, ASM might recommend a list of five exact match summaries, corresponding one-to-one with previously run queries (where ASM determines there is a benefit).

#### Mixed

A balance between predetermined and ad hoc queries (the default).

#### Adhoc

Use this setting to increase the coverage of a summary giving a potential performance gain for queries that have never been run before, but are closely related to previous system usage. However, the cost of this is that the individual performance gain for the previously run queries might not be as high.

For example, ASM might combine the five exact-match summaries to form fewer but more general summaries. These would provide benefit not only for the five previously run queries but also for a greater number of other potential queries (i.e. there would be a gain in overall coverage).

| Copyright © 1996, 2003 Oracle Corporation. All Rights Reserved. |
Home | Contents | Index