All sweeps have several attributes in common, such as the
time limit for the sweep query, scheduling, and filter conditions.
Opening a policy sweep
A policy sweep processes the objects in a database table
in an ongoing manner. In terms of implementation, a policy sweep consists
of two main components: a policy component and a sweep component.
Policies subscribe to sweeps in a many-to-one relationship: many policy
components might share a sweep component. When you create a policy
component, the appropriate sweep component is created automatically.
Opening a job sweep
A job sweep processes the objects in a database table in
one iteration.
Optimizing sweep performance by changing when filter conditions are evaluated
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.
Sweep scheduling
A sweep time period is a period in which the sweep can
run. You can specify multiple time periods for a sweep, which allows
flexibility in deciding when during the week a sweep runs and for
how long. If you do not specify any time periods, the sweep can run
at any time.
Sweep filter conditions
A filter condition narrows the scope of a sweep to include
only objects that meet specific criteria. The criteria is expressed
in terms of properties and values of the objects that are targeted
by the sweep. The syntax is a subset of the SQL syntax for the WHERE clause.