UAE · ENBook a demo
BankingEngineeringDecision-maker

Database Agent

Manages schemas, migrations and query performance.

Database AgentApplication Engineering
Industry
Banking
Department
Engineering
Team
Application Engineering
Kind
Decision-maker
Approver
Head of Technology Operations
Code
ENG-07

It designs schema changes and migrations for the bank's databases (customer, account, transaction and ledger stores), reviews slow queries and proposes indexes, and plans each migration step for lock time, table size and rollback around the core banking end-of-day batch. It decides whether a migration can run online or needs the maintenance window.

How it works

7 steps, and a person signs off before step 7.

  1. 01Looks it up

    Finds the record the request is about in the core banking system: the database catalogue, table sizes, query statistics and batch schedule..

  2. 02Reads the request

    Works out what is being asked and what a complete answer needs.

  3. 03Checks the facts

    Checks figures, dates and rules against the source records, not from memory.

  4. 04Forecasts, when it decides

    Projects what each option will cost or return before it recommends one.

  5. 05Works it through

    Prepares the draft, match, recommendation or reply, with its sources.

  6. 06Asks a person

    Hands the work to Head of Technology Operations with its reasoning before anything goes out.

  7. 07Acts

    Once approved, it acts in the code repository: it opens the migration change with its plan and rollback. and records what was done.

What it works with

Your knowledge, your systems, your people.

Knows

The database standards: change windows outside end-of-day and payment cut-offs, lock-time limits, ledger immutability (no updates or deletes to posted entries), encryption of personal data at rest, retention rules, and backup before migration.

Reads from

the core banking system: the database catalogue, table sizes, query statistics and batch schedule.

Acts in

the code repository: it opens the migration change with its plan and rollback.

Hands back

An object with steps (a list with step, online (true or false), expected_lock_seconds and rollback), indexes (a list with table, index and expected_gain), window (or null), backup_ref and risks.

Asks a person when

A migration needs the maintenance window, drops data, touches ledger or transaction tables, or changes encryption or retention.

ApproverHead of Technology Operations

Settings

Your limits, set by your managers.

SettingDefaultWhat it controls
Longest lock (seconds)2Online steps never lock longer.
Large table (rows)50000000Larger tables need batched changes.
Slow query (ms)300Queries slower than this are reviewed.
Maintenance windowSunday 01:00 to 04:00 local, outside end-of-day and payment cut-offsWhen offline steps run.
Delay before drops (days)30Columns and tables are dropped only after this.
Backfill batch (rows)5000Rows per backfill batch.

Limits are settings, not code: a manager changes them without a developer.

Rules it always follows

  • Online steps never lock for more than 2 seconds; tables over 50000000 rows change in batches of 5000.
  • Never update or delete posted ledger or transaction entries; corrections are new entries.
  • Offline steps run only in Sunday 01:00 to 04:00 local, outside end-of-day and payment cut-offs, never across end-of-day or a payment cut-off.
  • Drop columns and tables only 30 days after their last use, after a verified backup.
  • New columns holding personal data are encrypted at rest.
  • Review queries slower than 300 ms and propose indexes with their write cost.

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.

Database Agent · Banking | Basinwright Industries