SQL Database Server Maintenance Overview

To maintain a healthy and well-performing environment, the database server should run a number of scheduled maintenance jobs. Some jobs are included during installation as stored procedures in Forsta Plus databases, but are not started by default. Others can be added to fit individual setups. Included jobs and maintenance tasks are described in this part of the documentation.

For additional custom scripts used by Forsta Cloud Operations to maintain database servers, for example for shrinking databases, periodic clean-up of old log entries etc. please contact [e-mail].

Note: Forsta Plus does not by default hard-delete deleted projects. You must start and schedule the Forsta Plus Database Cleanup task in the Authoring interface under Admin > Maintenance > Database Cleanup to permanently delete projects from SQL.

1. To adjust the number of days that deleted projects are to be kept as soft-deleted, tune the DaysToKeepSurveyDatabasesForDeletedProjects in the sitewide System Configuration settings.
2. Go to Admin > Maintenance > Database Cleanup and change from “ASAP” to “Schedule for later execution”, then click OK and create an appropriate recurring schedule.

Keep in mind that this task does put stress on the system, so it is highly recommended to run it out of high peak hours.

Clearing Contents of Log Tables

The databases [confirm] and [confirmlog] contain task history and survey response history tables respectively. On a busy system, these databases will quickly grow substantially in size, and over time performance might deteriorate when reading from or writing to these databases.

To control the growth of the databases, some tables can be managed on a scheduled basis to reduce the number of stored rows. Please contact [e-mail] if you need help reducing the log table size in the confirm and confirmlog databases.