All applications583

Find your application

583 applications

Open full catalog

Browse applications by category or open the full catalog.

Database Administration
Start now
More

Features

Industries

Reference

More

Database Administration · Available now

Track database work from host record to service decision.

Database Administration brings a database instance, its host asset, service and responsible person into the same operating record. The team can follow backup runs by database and distinguish a completed run from one with recorded restore-test evidence.

Start now Download Proto
  • No per-user fees
  • Manual work is free
  • Configure it in Proto
OverviewBackup Runs to Verify
Database Administration · Backup runs

Backup Runs to Verify

Backup runs in one list

New backup run
Backup runs in view
6
Completed
6
Run numberDatabaseStarted atCompleted atRestore test atStatus
BR-22321shipments_prod on tracking host22 Oct23 Oct01 NovCompleted
BR-68424orders_replica on east standby27 Oct23 Oct31 OctCompleted
BR-86737inventory_reporting on west host04 Nov23 Oct29 OctCompleted
BR-91901orders_replica on east standby19 Oct20 Oct24 OctCompleted
BR-47444orders_prod on east primary16 Oct20 Oct27 OctCompleted
6 of 6 records
shipments_prod on tracking hostBackup runs · BR-22321
Completed
Started at22 Oct
Completed at23 Oct
Restore test at01 Nov
Review ChangeBR-22321 · shipments_prod on tracking host

Change Approver decides whether the reviewed service change may proceed.

Waiting for Change Approver
ApproveReturn
Example screen with sample data
Tables, ready to use
12
Saved views
13
Roles with set permissions
7
Reports and dashboards
8
Features

See the database work that needs attention

Every feature works on the same records. Pick one to see the screen your team works in.

Database Inventory

Connect each database to its host asset and accountable owner.

  • Service context
  • Host identity
  • Database identity
  • Database instances
  • Assets
  • Services
  • People
Explore database inventory
OverviewDatabase Inventory
Database Administration · Database Inventory

Database Inventory

Database instances

New
Database nameEngineVersionAssetOwner
orders_prod on east primaryRelational SQL engineRelational SQL engine 16.4Primary database host, east clusterAmina Duarte
orders_replica on east standbyTransactional SQL engineTransactional SQL engine 11.4Supplier portal database hostRavi Nair
billing_prod on ledger hostEnterprise SQL engineSQL Server 2022Warehouse query node 03Luis Romero
inventory_reporting on west hostWeb SQL engineWeb SQL engine 8.4Replica host, east clusterRavi Nair
identity_prod on directory hostDocument database engineDocument database engine 7.0Primary database host, east clusterLuis Romero
6 of 6 records
orders_prod on east primaryDatabase instances · DI-97721
EngineRelational SQL engine
VersionRelational SQL engine 16.4
AssetPrimary database host, east cluster
OwnerAmina Duarte
Example screen with sample data
Process

Follow each operating handoff

Database record to verified change ships ready to use. One step needs a named approval before the work moves on: Review Change (Change Approver).

Drag a card to another stage, or focus it and use the arrow keys. It updates to match the stage.

  1. Register Database

    Connect the database to its host asset and owner.

    shipments_prod on tracking hostBR-22321 · Database Administrator
    Register DatabaseBy Database Administrator

  2. Record Backup Run

    Capture the run outcome against the right database.

    shipments_prod on tracking hostBR-22321 · Database Administrator
    Record Backup RunBy Database Administrator

  3. Verify Backup Evidence

    Review the restore-test date for the completed run.

    shipments_prod on tracking hostBR-22321 · Backup Reviewer
    Verify Backup EvidenceBy Backup Reviewer

  4. Review Change

    Have the Change Approver decide on risk, timing and rollback.

    shipments_prod on tracking hostBR-22321 · Change Approver
    Review ChangeBy Change Approver
    ApprovalChange Approver decides whether the reviewed service change may proceed.

  5. Implement Change

    Carry out approved service work in its planned window.

    shipments_prod on tracking hostBR-22321 · Database Administrator
    Implement ChangeBy Database Administrator

  6. Verify Change

    Record the outcome after the work or rollback.

    shipments_prod on tracking hostBR-22321 · Change Approver
    Verify ChangeBy Change Approver

Start with Database and backup evidence

Inside a record

Connect the sources behind the record

Open any backup run to see the roles that work on it, its process stages and its approvals on one page.

  1. 1
    Record details

    Started at, Completed at and Restore test at.

  2. 2
    Linked records

    Records linked to this backup run.

  3. 3
    Who works on it

    Admin, Database Administrator and Backup Reviewer, each with their own permissions.

  4. 4
    Process stages

    Every status change, in order.

  5. 5
    Approvals

    Review Change, with who decides.

Backup Runs to Verifyshipments_prod on tracking host
Database Administration · Backup runs

shipments_prod on tracking host

Completed

Log activity
1
Record details
Started at22 Oct
Completed at23 Oct
Restore test at01 Nov
3

Who works on it

  • AdminManage Users, People, Services, Assets, database instances
  • Database AdministratorManage database instances, backup runs
  • Backup ReviewerManage backup runs
5

Approvals

  • Review ChangeChange Approver
    Approved
Example screen with sample data
Approvals

Give service changes a clear decision

Change review and request approval have different owners and working records.

OverviewApprovals
Database Administration · Overview

Approvals

Signed in as Change Approver

Waiting for you

4 To review1 Overdue2 Decided todayOnly mine
0 selectedApproveReturn
  • SR-92050Database restore
    Supplier portal databaseRequested by Sofia Bennett
    Submitted3dActions
  • SR-26355User access change
    Billing ledger databaseRequested by Ravi Nair
    Submitted1dActions
  • SR-15302Storage expansion
    Customer orders databaseRequested by Amina Duarte
    Submitted4dActions
  • SR-31540Read replica creation
    Analytics warehouseRequested by Sofia Bennett
    Submitted3dActions

Who approves what

DecisionApprover
Review ChangeHave the Change Approver decide on risk, timing and rollback.Change Approver
Approve ChangesChange Approver
Approve service requestsRequest Approver
3 approval rules · set per role in Proto
Example screen with sample data
Who can approve what
Roles

A workspace for each role

Everyone opens Database Administration to the work that is theirs. Pick a role to see what it starts with.

Admin

Maintains access and reference records across database operations.

  • Manage Users, People, Services, Assets, database instances
  • View backup runs, Incidents, Changes, service requests, Problems, integration receipts

Roles and permissions

Reports

Read outcomes from the working records

Answer operational questions from database, service and work records.

Overview
Database Administration · Overview

Database Administration dashboard

This quarter

Changes in view
6
Low
2
Medium
2
High
2

Backup runs by status

How far records got this quarter

StageReachedStep
Running39
Completed923%
Failed222%
Verified150%

Number of backup runs by status

Sample counts per stage

0
-40Running
-60Completed
-20Failed
0Verified
Example screen with sample data
  1. 01Backup outcomes by database

    Which databases have failed runs or a completed run awaiting evidence review?

  2. 02Backup run duration

    Compare recorded start and completion times for backup runs.

  3. 03Incident priority and status

    Which services carry active, high-priority incident work?

  4. 04Incident acknowledgment interval

    Compare opening and acknowledgment times for recorded incidents.

  5. 05Change decisions and risk

    Which planned service changes were approved, rejected or rolled back?

  6. 06Request completion by service

    Which service requests are still active and when did completed work finish?

  7. 07Open problems by owner

    See current problem status and assigned owner.

  8. 08Integration receipt outcomes

    Which provider events failed or were rejected during processing?

All reports and dashboards

Who it's for

Fit the process to your operations team

See how Database Administration fits your kind of team.

Managed database services

Keep each managed database connected to its host, owner and service work.

Internal IT database teams

Give internal operators a shared record of database work and service decisions.

Platform operations

Review database changes and backup evidence alongside service operations.

Controls

Keep the host and service context intact

Each stage of database record to verified change names the role that acts and the status it records, so a change is never anonymous.

OverviewDatabase record to verified change
Database Administration · Process

Database record to verified change

Each stage, the role that acts and the status it records

Process stages
12
Approval steps
1
Roles involved
6
Tables touched
5
Verify Backup Evidence
Backup Reviewer
StatusCompleted → Verified
Acknowledge Incident
Incident Responder
StatusOpen → Acknowledged
RecordsIncidents
Investigate Incident
Incident Responder
StatusAcknowledged → Investigating
RecordsIncidents
Database record to verified change
  1. Start
    Verify Backup EvidenceCompleted → Verified
    Backup Reviewer
  2. Step
    Acknowledge IncidentOpen → Acknowledged
    Incidents
  3. Step
    Investigate IncidentAcknowledged → Investigating
    Incidents
  4. Approval
    Review ChangeReview → Approved
    Changes
  5. Step
    Implement ChangeApproved → Implementing
    Changes
Example screen with sample data

See each stage in detail

AI agent

Ask Proto to prepare the next step

Ask Proto to prepare records and explain the next operational step.

It can

  • Database Administrator: Prepare an instance record from the known database name, host asset and owner.
  • Backup Reviewer: Find completed runs for a database and show the recorded restore-test date for review.
  • Incident Responder: Gather the service, asset, assignee and latest incident updates before a handoff.
  • Change Approver: Summarize a change's risk, planned window and rollback plan for a decision.

Stays with a person

  • Proto can organize the relevant records and help prepare an action.
  • A human approver decides on a change or submitted request, and a reviewer checks restore-test evidence before verification.
  • The operating team remains responsible for work on the database and for confirming external event outcomes.
  • Usage depends on the work Proto performs and the connected services involved.

Set up an agent

Integrations

Connects to the tools you use

Set up connections through ERP.AI and Proto workflows, with every change logged.

  • Database Administration
  • Backup execution system
  • Monitoring source
  • Event provider
  • Identity source
Data model

Your data, in tables you can change

Every record lives in a table you can see, extend and export. Add fields or whole tables in Proto.

Browse all 12 tables
12tables
  • Database Inventory4
  • Backup Evidence4
  • Incident Response6
  • Change Control5
  • Service Requests4
  • Service Evidence7
Implementation

Roll out one team at a time

Start with one team and one process, then add the rest once the basics are running.

  1. Establish ownership

    Add users, people and services with clear owners and criticality.

  2. Map databases

    Connect assets to services and database instances to assets and people.

  3. Review evidence

    Record a representative backup run and check its database, outcome and restore-test date.

  4. Rehearse service work

    Open an incident, review a change and approve a submitted request with the people who will own those decisions.

  5. Connect sources

    Bring external events and operational signals into the corresponding records and inspect failed receipts.

Read the implementation plan

Pricing

$0per user

The base account and everyday work in the ERP.AI app are free, for every user.

  • No per-user or per-seat fees
  • Viewing, editing, approving and exporting records in the app is free
  • Pay only for machine work: API calls, imports, workflows and AI agents
  • Prepaid credits from $5. Purchased credits never expire

Pricing details

Machine work rate card Included per $1 of credit

Machine work rate card
UsagePer $1
Record reads (list, filter, get)20,000
Search or aggregate queries4,000
Record writes4,000
Imported or synced records200,000
Workflow runs2,000
AI agent runs2,000
Scheduled jobs or webhooks20,000
File uploads (MB)2,000
CSV or PDF exports100
FAQ

Questions, answered

Scope, rollout and pricing for Database Administration.

All questions
How do I get started?

Click Get started, then use Proto to configure Database Administration for your business. Begin with a service, its host asset, a database instance and a recent backup run. Rehearse a review and an incident before expanding the scope.

How do we identify the database behind a backup?

Each backup run references a database instance. That instance references a host asset and an owner.

Does a completed run mean the restore was tested?

A run can be completed before it is verified. Check the restore-test evidence before recording its date; a completed run with that evidence moves to verified.

Who decides whether a change proceeds?

The Change Approver reviews the service, risk, planned window and rollback plan, then records approval or rejection.

How does a database incident reach an owner?

The incident records its service, asset and assigned person. The newly opened incident receives an acknowledgment time; the responder records authored updates as work proceeds.

Can a recurring issue stay visible after incident resolution?

A problem record can retain the statement, owner, root cause and investigation status under the affected service.

How do service requests move into work?

The Request Approver decides on submitted work. Approved requests can then move into progress and completion.

What is an integration receipt used for?

It records the provider, external event identity, receipt time, payload hash and processing outcome for reconciliation.

What should we prepare before connecting a monitoring source?

Confirm service names, host asset tags and the person who responds to incidents so incoming signals can be mapped to the right operational context.

Set up Database Administration your way.

Start free, then use Proto to change fields, steps and approvals before your team goes live.

Start now Download Proto

How to get started

A personal agent for your business

Get started with Proto

Your app is selected. Download Proto, then open it with this context.

Selected appDatabase Administration

Choose your computer’s platform.

Download Proto

Install Proto, then return to this panel.

Already installed? Open Proto

Free to use. Your own model provider may charge for usage.