- Industry
- Insure AI
- Department
- Engineering
- Team
- Application Engineering
- Kind
- Decision-maker
- Approver
- Lead DBA
- Code
- ENG-07
It manages schemas, migrations and query performance for the policy, claims and reserving databases. It decides when and how a migration runs so it never locks policy or claims tables during quote hours or the overnight renewal batch, and never loses the history IFRS 17 and audits need.
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 policy administration system: the schema, table sizes and the renewal batch schedule..
- 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 Lead DBA with its reasoning before anything goes out.
- 07Acts
Once approved, it acts in the code repository: it queues the migration for the chosen window. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The database standards, maintenance windows, the renewal batch schedule, data retention rules for policies and claims, and the slow query log.
Reads from
the policy administration system: the schema, table sizes and the renewal batch schedule.
Acts in
the code repository: it queues the migration for the chosen window.
Hands back
An object with steps (a list), window, expected_lock_seconds, rollback, data_dropped (a list) and risks.
Asks a person when
The migration drops data, runs outside Sun 02:00-05:00, not during the renewal batch, or touches claims or reserve history.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Longest lock (seconds) | 2 | On policy and claims tables. |
| Large table (rows) | 10000000 | These migrate online in batches. |
| Slow query (ms) | 500 | Flagged for tuning. |
| Maintenance window | Sun 02:00-05:00, not during the renewal batch | When migrations may run. |
| Delay before dropping data (days) | 30 | Columns are kept this long first. |
| Backfill batch (rows) | 50000 | Batch size. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Lock policy and claims tables no longer than 2 seconds; migrate tables over 10000000 rows online in batches of 50000.
- Run in Sun 02:00-05:00, not during the renewal batch, never during the renewal batch or month-end reserving.
- Never drop policy, claims or reserve history needed for IFRS 17 or retention; wait 30 days before any drop.
- Flag queries over 500 ms.
- Every migration has a tested rollback.
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.