How to Create The Archer Provided Maintenance Jobs for The Instance Database

[KB-Sync1]

Article Number

000039933

Applies To

Product(s): Archer
Version(s): All Versions
Primary Deployment: On Premises

---

Description

The intent of this article is to provide a quick guide to set up and configure the default Maintenance Jobs for the Archer Instance Database. It is recommended to re-deploy these jobs with each Archer upgrade so that any changes to the jobs are included.

Resolution

Follow the steps below:

1. Login to SQL Server Management Studio with a user who has write access to MSDB. The server must be where your Archer Instance database resides.

2. Run the jobDeployScript.sql script against the Instance database. This script can be found in the Tools folder on any Archer install. For example: <drive>:\Program Files\Archer\Tools\jobDeployScript.sql

0EMVM000005yPBx.png

3. Observe that the Jobs are created. Here is what the script creates:
0EMVM000005yTaX.png

4. Configure the time of each job by modifying the schedule, if desired. Open the Job and then click on Schedules. 

0EMVM000005yME6.png

5. Click Edit then set the time for the job to run.

0EMVM000005yWa1.png

6. Configure the time for all three Jobs, if needed.

7. Each of these jobs calls a stored procedure that is part of the Instance database. Below is the stored procedure run by each job (in case it is needed to run the stored procedures manually):

• Archer Database Heap Table Maintenance (archerinstance):

exec usp_rebuild_heap_tables

• Archer Database Index Rebuild (archerinstance):

exec usp_reindex_db_2

• Archer Database Statistics Update (archerinstance):

exec usp_update_statistics

8. The details can also be found by opening the Step.0EMVM000005yXnp.png

9. Once the schedule is set up and the jobs have run, you can confirm that they were executed by navigating to the Job Activity Monitor.

0EMVM000005yYIU.png

10. Right-click on the job and select View history.

0EMVM000005yXFy.png

11. Observe the times each job has run and if it was successful.

0EMVM000005yLDG.png