Consider the following information when scheduling tasks:
- Maintenance tasks create a significant load on the database and server. Therefore, schedule the tasks at a time when there is not much user activity.
- Avoid scheduling these tasks during other heavy load tasks, such as database backup.
- Calculations using Today should be scheduled after midnight so that the new date is in effect. Between midnight and the time the task is scheduled, cells with functions using Today will show yesterday's value. Therefore, schedule tasks before users start accessing the system each day. These tasks should run only once every 24 hours.
- Resolve Version Dates should be scheduled after midnight.
- To bind the start of one task to the completion of another task [for example, Schedule Periodic Update (Portfolios) after Import Data], schedule them to start 1 minute apart. The PPM Service performs only one such task at a time, and will wait for the completion of Import Data before starting Periodic Update (Portfolios).
- Schedule Import Data after the psraw_ tables are populated. However, you cannot bind a task to an external batch process. If you know the time the external batch process will complete, you can schedule a task to run after that time, or you can add the command-line psTriggerImport.exe (with the appropriate parameter) to your external batch file.
- Schedule both Frequent and Periodic Update (Portfolios) after Import Data and calculations using Today so that the new data is used when the Dynamic portfolios are refreshed.
- Recalculating database statistics (in Oracle) is time consuming, so do not run this task too often. It is recommended to run this task once every 24 hours.
- Although there are no constraints on scheduling Log Files Maintenance and Audit Log Cleanup, it is recommended to set this task to a different schedule than the other tasks.
- It is not recommended to run Recalculate Temp Statistics more frequently than every 30 minutes.