![]() ![]() |
|
Help for Process Analyzer Administration and Configuration | |
Search | Index | |
![]() |
|
![]() |
![]() |
![]() |
Pruning the Process Analyzer data warehouseOver time, the database tables consume a significant amount of storage space, so a strategy is required to remove data that are no longer needed. Pruning the data warehouseThe Process Analyzer collects workflow, configuration, resource, and event data, and stores them in the data warehouse on the Process Analyzer Engine. The Process Analyzer then processes these data and stores the results in the fact and dimension tables in the data mart. Once the data have been processed, they are no longer needed. Therefore, once a workflow termination event has been processed, data pertaining to that workflow can be pruned from the data warehouse. NOTE Pruning the data warehouse can use a large amount of space in the SQL Server transaction log. Make sure that the transaction log is large enough or is set to grow automatically as needed. Alternatively, you can prune the data warehouse more often than is scheduled by default. To facilitate the pruning process, the pruning job, , is installed as a local package on the SQL Server. Note that is initially installed in disabled mode.To prune the data warehouse CAUTION Be sure that the job occurs at least one hour after the ProcessCubes job.
If you cancel the Prune VMAEDW job When you start the job, the Process Analyzer Engine automatically pauses the Publisher service. If you cancel the job before it completes, the Publisher remains paused and will not resume. To resume the Publisher, you must take one of the following steps.
|
![]() |
|
![]() |
|