To optimize sweep performance, you can optionally make
the filter conditions for the sweep a part of the WHERE clause
of the sweep query. This inclusion means that the sweep retrieves
only those database rows that satisfy the filter conditions. The default
behavior is non-inclusion: a sweep retrieves all potentially relevant
database table rows and evaluates the filter conditions for each row.
Before you begin
Create the appropriate database indexes for the sweep. For
more information, see
Creating an index to improve sweep performance.
Without the appropriate indexes, sweep performance is not improved
by including filter conditions in the sweep query.
About this task
You include filter conditions in the sweep query by setting
the time limit for the query to some value other than 0. If the query
runs longer than the specified time limit for any particular sweep
iteration, the sweep iteration proceeds as if no time limit were set.
(That is, the sweep iteration proceeds in the usual default way with
no filter conditions included in the query.)
Tip: Initially
set the time limit for the query to a fairly low value, such as 30
seconds. Adjust the value later as sweep performance dictates. For
information about monitoring sweep performance, see
Sweep iteration progress monitoring.
Restriction: Some properties, such as owner,
are non-queryable, which means that they have a value of false for
the IsSearchable metadata attribute. References
to non-queryable properties are not included in the WHERE clause
of a query (regardless of the time limit that you set for the query).
The filter condition owner='jsmith', for example,
does not get included in the sweep query.
Procedure
To set the time limit for the sweep query:
- Open the sweep in the administration console:
- On the Properties tab, change the value of the Filtered
Query Timeout property.
- Save your changes.