PI AF server's SQL Server maintenance jobs

Note: The following features are not supported if using one of the cloud database platforms: AF Collectives and backups during upgrade. SQL Server maintenance jobs can only be run by cloud platforms that supports jobs. As an alternative, you can run the maintenance job manually using the AF Diagnostic utility's /MaintenanceJob parameter. See AFDiag utility parameters.

During an AF SQL Database install, two SQL Server jobs are created: AVEVA AF Maintenance and AVEVA Backup. By default, the AVEVA AF Maintenance job is not enabled, while the AVEVA Backup job is enabled. Each job has a defined schedule that indicates when the job will be run if the job is enabled.

You can reconfigure these jobs to run on a specified schedule or to not run at all. Schedule these jobs, or your own, during non-busy times. If you prefer to write your own maintenance jobs, you can delete these jobs and write your own. However, be aware that these jobs are re-created upon your next upgrade.

Note: The time required to complete AVEVA AF maintenance jobs is variable and depends on the system resources available. In particular, the number of objects within the SQL database, the applications running on your server, and how recently maintenance jobs were last run all factor into the length of time required. Ensure that you plan and schedule accordingly.

As standard practice and to guarantee compatibility during upgrades, use data access tools like AF SDK and PI OLEDB Enterprise; do not directly query the PI AF SQL Server database using SQL. For more information, see the Knowledge Base article: Direct reading or manipulation of the PI AF SQL Database (PIFD) is not supported.

Note: The tasks performed by the maintenance jobs are subject to change with each release. Administrators who have customized the maintenance activities should review the changes in the AVEVA-provided maintenance jobs after any upgrade.