Syncfish strongly recommend a SQL DBA is engaged to review a number of SQL health and performance settings once CI Sync has been setup.
-
Validate the CI Sync RecVer database is in Simple Recovery Mode.
-
Setup a Rebuild Index Maintenance Plan (on the RecVer DB & potentially the Source System DB).
-
Setup an Update Statistics Maintenance Plan (on the RecVer DB & potentially the Source System DB).
-
Several other general suggestions for SQL database health
Each of the above are explained in the Syncfish Knowledge Base Article titled: How-to - Configure SQL Maintenance Plans on SQL database(s) for SQL based Source Systems Plan
Important
The optimal sequence from discovery through to sync are as follows:
-
Lansweeper completes its scans.
-
The SQL Server maintenance plans run.
-
The CISync job/s run.
Syncfish recommend assessing your Lansweeper scanning schedules to find a daily window where Lansweeper is not scanning (i.e. a time when the Lansweeper database is not being modified). You should schedule the SQL maintenance plans to executing during that window, and then schedule CI Sync job/s to run after the SQL maintenance plans have completed.