Data is rarely lost all at once. It first spreads across spreadsheets, then reports slow down and no one has tested a backup restore. I build databases that stop this: structure, speed and recovery.
One fact, one place
A customer, item or order is entered once. When the same fact lives in several spreadsheets, differences eventually appear.
Measured, not guessed
The slowest queries are measured before and after the work, so you receive a difference in seconds.
A backup that restores
A backup is valuable only after it restores to an empty server and the recovery time is measured.
Where this makes sense
Excel has outgrown itself
Data moves to a database with a simple entry and search screen, so everyone uses the same current information.
The system has become slow
I find slow queries, add missing indexes and correct what the database cannot optimise by itself.
A legacy database
Its structure is documented and data can move to a database that can be maintained.
Data in several systems
Sales, warehouse and accounting data can be joined through a common key or copied to a reporting database.
Technologies
I work with MySQL, MariaDB, Microsoft SQL Server, PostgreSQL and SQLite. The choice depends on your system, data volume and hosting environment.
A database rarely stands alone. I also build desktop software, websites and AI features that use its data.
Pricing
Prices are public so you can see the order of magnitude. The final price and deadline follow the paid database review.
First step: database review
I do not quote a fixed price for a database I have not seen. The review takes two working days, has a fixed price and produces a written finding that remains yours.
- Structure: data location, duplicates and missing relationships.
- Speed: slow queries, missing indexes and measurable improvement.
- Backups: their age and whether they really restore.
- Access: who can read or change data.
- Priorities: work ordered by impact and estimated duration.
Commitments, scope and preparation
Clear limits
I am not an around the clock server administrator and I do not work with Oracle or Db2. I do not recommend a new database when an index, report or data cleanup solves the problem better.
Ownership, access and data
- The database, schema and scripts are yours.
- Accounts and server are in your name.
- Work is tested on a copy whenever possible, with a backup and rollback path before every change.
- Any data copy is agreed in advance and sensitive data can be replaced with samples.
Frequently asked questions
Not sure what the real problem is?
Describe the slow system, duplicate data, fear of loss or an Excel file that has outgrown itself. I will tell you whether it needs a review, a small improvement or no change at all.
Send an enquiry