Complete AI Training
Sign inGet my AI kit

Your job's AI kit

Get your AI kit

Tell us who you are and what you do. We show you your kit right away and email you the link: skills, prompts, AI agents, MCP servers and courses for your job.

500+ jobs ready, and we make a kit for any other job. No payment needed to look.

Share

AI agent for database administrators

Database Capacity and Growth Agent

No database hits a capacity limit unplanned

Database Capacity and Growth Agent: what goes in, what the agent does and what you get

What it does

Databases grow quietly, and without planning they hit storage or memory limits at the worst moment. Each week this agent collects size, growth rate, connection counts and resource use for every database and forecasts when each will reach a limit. It excludes one-off jumps, such as a bulk load, so the trend is not distorted. For predictable growth it proposes actions such as archiving old data, adding storage or adjusting settings. Before proposing an archive, it checks that the data is past its retention date and not referenced anywhere. If a forecast shows a limit inside the warning window, it drafts a plan with options and lead times. You approve archiving and capacity changes. Edge case: a database that grows only at month end is forecast on its monthly pattern, not a daily average.

How it works

Follow the arrows from top to bottom. The orange dashed arrow is the loop: when a check fails, the agent goes back and tries again.

Start and resultWhat it doesA check on its own workWaits for your OKGoes back and retries
Yes, continueApprovedNo 1 STARTS WHEN Weekly capacity check 2 USES A TOOL Collect size, growth and resource metrics 3 DOES Forecast time to each limit, excluding one-offspikes 4 CHECKS THE RESULT Is any limit forecast within the warning window? If not: log a healthy result and stop. Back to step 2. 5 DOES Propose archiving, storage or setting changes 6 USES A TOOL Confirm archiving candidates are past retention andunreferenced 7 YOU APPROVE DBA approves the capacity plan 8 RESULT Capacity plan or healthy log
Read the steps as a list
  1. Weekly capacity check
  2. Collect size, growth and resource metrics
  3. Forecast time to each limit, excluding one-off spikes
  4. Is any limit forecast within the warning window?If not: log a healthy result and stop. Back to step 2.
  5. Propose archiving, storage or setting changes
  6. Confirm archiving candidates are past retention and unreferenced
  7. DBA approves the capacity planThe agent waits here for your OK.
  8. Capacity plan or healthy log

How it decides

It forecasts from steady growth, excluding one-off spikes, and recommends action when a limit is forecast within the warning window.

  • Exclude one-off bulk loads from the trend
  • Archive only data past retention and unreferenced
  • Warn when a limit is within the window

Make it yours

Every agent is a starting point. You choose these settings for your own situation.

  • Warning window (default 14 days)
  • Retention periods
  • Databases in scope
  • Preferred actions order

What keeps you in control

It always asks you first

  • Archiving data
  • Changing storage or database settings

Hard limits

  • Never deletes data; archives only with approval
  • Confirms retention before any archive

It stops when

  • Done: capacity healthy or plan approved
  • Stop: metrics history is too short to forecast

Set it up

We guide you through the set-up, step by step

Members get the full set-up guide for this agent. No technical skills needed: you copy, paste and upload.

10 minto set it up in your AI
5 AIsChatGPT, Claude, Copilot, Gemini, Grok
  • One set of instructions to paste into your AI, with the clicks for ChatGPT, Claude, Microsoft 365 Copilot, Gemini and Grok
  • The agent then walks you through connecting your own data, one source at a time
  • A downloadable copy with the flow chart, the rules and the full guide
Get access to this agent

An example run

What happensIn the week of January 15 at Riverside Logistics, the logs database grew 4 GB a day and was forecast to fill its disk in 9 days, inside the 14-day window. A 60 GB migration spike was excluded. The first archive set included rows a billing job still read, so the reference check failed. The agent narrowed it to unreferenced entries past 90 days, freeing 140 GB. The DBA approved it.

More agents for database administrators