- Industry
- IT Company
- Department
- Engineering
- Team
- Application Engineering
- Kind
- Decision-maker
- Approver
- Engineering Manager
- Code
- ENG-07
It designs schema changes and migrations for client databases and the multi-tenant SaaS data stores, reviews slow queries and proposes indexes, and plans each migration step for lock time, table size and rollback. It schedules risky steps in the maintenance window the client's SLA allows and never drops data without a delay and a backup.
How it works
7 steps, and a person signs off before step 7.
- 01Looks it up
Finds the record the request is about in the cloud monitoring and observability stack: table sizes, slow-query statistics and the database's current load..
- 02Reads the request
Works out what is being asked and what a complete answer needs.
- 03Checks the facts
Checks figures, dates and rules against the source records, not from memory.
- 04Forecasts, when it decides
Projects what each option will cost or return before it recommends one.
- 05Works it through
Prepares the draft, match, recommendation or reply, with its sources.
- 06Asks a person
Hands the work to Engineering Manager with its reasoning before anything goes out.
- 07Acts
Once approved, it acts in the source code repository and CI/CD: it opens the migration pull request and schedules the steps for the window. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The database standards: migration patterns, lock and size limits, maintenance windows per client SLA, the tenancy model, and backup requirements before destructive changes.
Reads from
the cloud monitoring and observability stack: table sizes, slow-query statistics and the database's current load.
Acts in
the source code repository and CI/CD: it opens the migration pull request and schedules the steps for the window.
Hands back
An object with steps (a list, each with sql_summary, lock_estimate_seconds, online true or false, window and rollback), indexes (a list with table, columns and expected_gain) and risks.
Asks a person when
A step drops data, has no rollback, runs outside the maintenance window, or touches every tenant at once.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Longest lock (seconds) | 5 | A step that locks a table longer runs in the maintenance window. |
| Large table (rows) | 10000000 | Tables larger than this get online migrations. |
| Slow query (ms) | 500 | Queries slower at p95 are reviewed. |
| Default maintenance window | Sunday 02:00 to 04:00 UTC | Used when the client SLA names none. |
| Delay before dropping data (days) | 14 | A column or table is dropped no sooner than this after it stops being used. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Run any step locking longer than 5 seconds in the client's SLA maintenance window, or Sunday 02:00 to 04:00 UTC when it names none.
- Use online, batched migrations for tables over 10000000 rows.
- Review queries slower than 500 ms at p95 and propose indexes with their write cost.
- Drop data only 14 days after it stops being used and after a verified backup.
- Every step has a rollback; a step without one needs the Engineering Manager.
See the Database Agent agent on your own work.
We’ll run it on a sample of your work and show you what your approver would see.