The infoRouter database stores all metadata for every document in the system, including author, creation date, check-out status, access permissions, Custom Property values, and hundreds of other data points per document. A database that is not maintained will degrade in performance over time, produce errors, and eventually put your data at risk.
Database maintenance is the responsibility of the customer's IT team. It falls outside the scope of infoRouter's standard support agreement. This guide explains what needs to happen and provides links to platform-specific resources.
Key Takeaways
- An unmaintained infoRouter database degrades in performance over time due to index fragmentation, stale statistics, and unchecked growth.
- Database maintenance including index rebuilds, statistics updates, and integrity checks should be automated on nightly, weekly, and monthly schedules.
- Database maintenance is the responsibility of the customer's IT team and falls outside the scope of infoRouter's standard support agreement.
- A database that performs well in year one can become noticeably slower by year two if no database maintenance is performed.
Supported Database Platforms
- Microsoft SQL Server
- MySQL
Why Database Maintenance Matters
An unmaintained database accumulates problems:
- Index fragmentation slows query performance, which directly affects search speed and page load times in infoRouter
- Unchecked growth consumes disk space and increases backup times
- Stale statistics cause the query optimizer to choose inefficient execution plans
- Missing integrity checks leave data corruption undetected until it causes failures
These problems compound over time. A database that performs well in year one can become noticeably slower by year two if no maintenance is performed.
What a Maintenance Plan Should Include
At minimum, your database maintenance plan should cover:
- Index rebuilds or reorganization. Run weekly or as needed based on fragmentation levels.
- Statistics updates. Ensure the query optimizer has current information.
- Integrity checks (DBCC CHECKDB for SQL Server). Run weekly to detect corruption early.
- Log management. Prevent transaction logs from consuming all available disk space.
- Backups. See the infoRouter Database Backup Guide.
Schedule maintenance tasks to run automatically on a nightly, weekly, and monthly basis. Do not rely on manual execution.
Platform-Specific Resources
Support Scope
infoRouter support covers the infoRouter application itself. Database maintenance and administration, including backups, performance tuning, index management, and routine maintenance, are the responsibility of the customer's database administrator or IT team.
If you do not have a dedicated DBA, the maintenance plan guides linked above provide step-by-step instructions for automating the essential tasks.
Frequently Asked Questions
- Is database maintenance included in the infoRouter support agreement?
- No. Database maintenance and administration are the responsibility of the customer's IT team or database administrator. infoRouter support covers the application itself.
- How quickly will I notice performance degradation without maintenance?
- A database that performs well in year one can become noticeably slower by year two if no maintenance is performed. Index fragmentation and stale statistics compound over time.
- What is the minimum maintenance I should be doing?
- At minimum, schedule index rebuilds weekly, update statistics regularly, run integrity checks weekly, and manage transaction logs to prevent them from consuming all disk space.
- Does this apply to both SQL Server and MySQL?
- Yes. Both platforms require regular maintenance. The specific tools differ, but the tasks (index management, statistics updates, integrity checks, and log management) apply to both.