Database Maintenance
Database maintenance is the regular review of an application’s data layer. It covers backups and restore tests, slow queries, indexes, table growth, storage headroom and data integrity.
Backups and restore tests
A backup file is not proof of a backup. Until it has been restored into a separate copy and the data opened, its usefulness is unknown. Restore tests run on a schedule.
The regular review
Changes that need approval
Nothing is deleted on our own judgement. Old data is archived and not dropped, and structural changes are applied to a copy first. A record from several years ago may still be needed for the accounts.
Frequently asked questions
How often does a database need maintenance?
It depends on how the application is used. A monthly review with restore tests suits many business applications, and systems taking orders through the day gain from more frequent slow-query checks.
Our database is on shared hosting. Does that limit the work?
Somewhat. Shared plans restrict configuration and sometimes hide the slow-query log, so part of the work becomes a recommendation to move.
Can data be cleaned up without downtime?
Usually, by archiving in small batches during quieter hours. Structural changes to very large tables may still need a short agreed window.
Do you work with MySQL and PostgreSQL?
Yes, and with MariaDB, which behaves much the same. An application on another engine is looked at case by case before any commitment.
Tell us what you need.
Share your requirements and one of our engineers will come back to you within one business day.
- No obligation
- A reply within one business day
- Your details stay private
Start with your requirements
Seven short steps that tell us what you need. An engineer reads them before getting in touch.
Share your requirements