At some point, such as at the end of a development period,
you might decide to initialize or remove an isolated region of the
workflow database. The pruning process removes all workflows, work
items, queues, and so on, that pertain to that isolated region.
If Case Analyzer is
collecting data from that isolated region, you must remove all the
data that is associated with the isolated region from the Case Analyzer store.
Important: Depending on the amount of data that is involved, pruning the isolated region
can use a large amount of space in the database transaction log. Make sure that the transaction log
is large enough or is set to grow automatically as needed, and that there is sufficient disk space
on the data file drive. In addition, make sure that the disk drive that contains the transaction log
has sufficient space.
Cube processing, pruning events,
and pruning an isolated region require exclusive use of the Case Analyzer store, and can degrade Case Analyzer performance. Schedule these
actions to run during off-hours.
To prune isolated region data
from a Case Analyzer store:
- Select the Case Analyzer folder.
- From the Action menu, select Prune
Isolated Region.
- Enter the number of the isolated region whose data you
want to prune.
- Click Next.
- Verify the isolated region.
Important: Pruning
isolated region data deletes all data in the Case Analyzer store that is related to
the isolated region.
- Click Prune to start the job. Process
Task Manager processes the job in the background, and displays a message
in the Message pane when the job is complete.
Attention: You must run the Process
Cubes action after pruning an isolated region.