UAE · ENBook a demo
Oil & GasEngineeringDecision-maker

Database Agent

Manages schemas, migrations and query performance.

Database AgentApplication Engineering
Industry
Oil & Gas
Department
Engineering
Team
Application Engineering
Kind
Decision-maker
Approver
Lead DBA
Code
ENG-07

It designs schema changes and migrations for the operational and commercial databases, such as the production data mart, the CMMS reporting store and the hydrocarbon accounting extracts, and reviews slow queries. It decides whether a migration runs online now, waits for the window clear of month-end allocation close, or must be split, and schedules it.

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 database's catalogue and query statistics: table sizes, locks and slow queries..

  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 Lead DBA with its reasoning before anything goes out.

  7. 07Acts

    Once approved, it acts in the migration tool: it schedules the migration steps in the chosen window. and records what was done.

What it works with

Your knowledge, your systems, your people.

Knows

The database standards: migration patterns, lock limits, the month-end allocation close calendar, retention rules for regulatory production records and rollback plans.

Reads from

the database's catalogue and query statistics: table sizes, locks and slow queries.

Acts in

the migration tool: it schedules the migration steps in the chosen window.

Hands back

An object with steps (with lock estimate), decision (online now, window or split), scheduled_at, rollback and indexes.

Asks a person when

The migration touches regulatory records, falls in the close freeze, or cannot be rolled back.

ApproverLead DBA

Settings

Your limits, set by your managers.

SettingDefaultWhat it controls
Longest lock (seconds)5Online migrations stay under this.
Large table (rows)10000000Historian extracts grow fast.
Maintenance windowSunday 02:00 to 04:00 UTCWhen long migrations run.
Freeze around month-end close (days)5No migration in the first days of the month while allocation closes.
Delay before dropping (days)30Columns and tables wait this long before removal.

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

Rules it always follows

  • Run online only when locks stay under 5 seconds.
  • Split or schedule migrations on tables over 10000000 rows into Sunday 02:00 to 04:00 UTC.
  • Schedule nothing in the first 5 days of the month on databases that feed allocation or regulatory reporting.
  • Never drop regulatory production or emissions records; wait 30 days before any other drop.

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 · Oil & Gas | Basinwright Industries