Maintenance gives administrators the housekeeping tools that keep OptimiDoc running efficiently: database information, database optimisation, old-job cleanup, and credential repair. Every action on this page is run manually, on demand — there is no built-in scheduler.
Screenshot: Maintenance view
Overview
The Maintenance page presents four cards, each a self-contained tool: Database Info, Database Optimisation, Clear Old Jobs, and Fix Credentials. Regular maintenance helps prevent database bloat, keeps queries fast, and repairs data-integrity issues that can accumulate over time. Because OptimiDoc does not schedule these tasks itself, decide on a cadence and either run them by hand or drive the database operations from a SQL Server Agent job.
Accessing Maintenance
-
Log in to the OptimiDoc web interface as an administrator.
-
Navigate to Diagnostics > Maintenance in the left sidebar.
Database Info
The Database Info card reports the live status of the OptimiDoc database:
|
Field |
Description |
|---|---|
|
Server |
The SQL Server instance hosting the database. |
|
Database |
The name of the OptimiDoc database. |
|
Size |
The current size of the database, in megabytes. |
Monitor the size over time. Rapid growth usually means job retention is too long or old data needs purging — address it with Clear Old Jobs or shorter hold periods in Print Settings.
Database Optimisation
The Database Optimisation card runs maintenance operations against the database to keep query performance healthy. Choose one of three levels from the dropdown, then click Run Optimisation. The operation runs synchronously and reports its elapsed time on completion.
|
Level |
What it does |
Typical impact |
|---|---|---|
|
Level 1 — Update statistics |
Refreshes the query optimiser's statistics so it can choose efficient plans. The lightest option. |
Fast; minimal impact |
|
Level 2 — Rebuild indexes |
Rebuilds table indexes to reduce fragmentation. |
Moderate; brief impact during execution |
|
Level 3 — Full maintenance |
The most thorough option, performing a full-scan statistics update for the most accurate optimiser data. |
Longest running; run in a maintenance window |
Suggested cadence: Level 1 weekly, Level 2 monthly, Level 3 quarterly or after large data changes (for example, after purging old jobs). Run heavier levels during off-peak hours.
Clear Old Jobs
The Clear Old Jobs card permanently deletes job records older than a chosen age, together with their associated copies and accounting records. Use it to control database size and enforce a retention policy.
|
Setting |
Description |
|---|---|
|
Delete jobs older than (days) |
Minimum age of the job records to delete. Defaults to 365; the minimum accepted value is 30. |
-
Enter the age in days (for example, 365 to remove jobs older than one year).
-
Click Clear Jobs and confirm in the dialog.
-
A message reports how many records were deleted.
This operation is irreversible. Deleted job, copy, and accounting records cannot be recovered. Make sure any required report exports are complete, and back up the database, before running it.
Fix Credentials
The Fix Credentials card scans the user database for credential inconsistencies and repairs them. It is useful after:
-
bulk user imports that may have created duplicate or malformed credential entries,
-
database migrations or restores that introduced integrity issues, or
-
card-reader configuration changes that affect stored card-number formats.
Click Run Fix to scan and repair. The operation is safe to run at any time and does not alter valid credential data.
Scheduling and Backups
OptimiDoc does not run these tasks on a timer and has no built-in backup tool, so plan around the platform:
-
Drive routine database optimisation from a SQL Server Agent job if you want it automated, or run the levels by hand on the cadence above.
-
Configure daily SQL Server backups, store them on separate storage from the database server, and test restoration periodically.
-
Back up the spooler directory if it holds jobs that must survive a disaster-recovery scenario.
-
Always take a database backup before Level 3 optimisation or Clear Old Jobs.
Related articles