Ongoing Database Operations

Managed DBA for production databases.

Give monitoring, maintenance, performance, and recovery planning a clear owner. JusDB works alongside your engineers with responsibilities and coverage defined for your environment.

Discuss Your DBA Coverage View Managed DBA Plans

A platform team needs an owner

Define who maintains the databases while your engineers build and operate the application.

An existing DBA needs capacity

Add scoped engineering work, specialist reviews, and coverage around your own team.

A growing product needs a routine

Make performance, recovery readiness, and capacity part of ongoing operations.

Example Responsibility Map

See who owns the work.

This illustrative split shows how a managed relationship can work. Your proposal confirms the included tasks, approval boundaries, covered hours, and reporting cadence.

Monitoring & incidents

JusDB work
Review agreed alerts, investigate during covered hours, and follow the escalation runbook.
Your team
Provide application context, business priorities, escalation contacts, and approval for actions outside the runbook.

Example record: Incident timeline, actions taken, and follow-up owners

Maintenance & performance

JusDB work
Review queries, patches, and capacity; propose changes with validation and rollback steps.
Your team
Approve the change window and application impact; complete application-side testing.

Example record: Prioritized work queue and approved change records

Backups & recovery

JusDB work
Review backup health and carry out agreed restore or failover exercises in a suitable environment.
Your team
Set recovery priorities, approve test scope, and validate the recovered application's behavior.

Example record: Restore-test evidence, recovery gaps, and an updated runbook

Service review & handover

JusDB work
Summarize operational work, open risks, and capacity trends; maintain the agreed documentation.
Your team
Prioritize the next work, review service needs, and identify changes in ownership or access.

Example record: Service summary, decisions, and named next actions

Monitoring is separate from human response. Acknowledgement targets apply within the agreed coverage; mitigation and resolution depend on the incident. Planned engineering work also has an agreed allowance.

Onboarding & Access

Prepare before coverage begins.

The onboarding sequence and schedule depend on your environment and approval process. The service agreement confirms when ongoing responsibilities begin.

  1. Agree the scope

    Confirm databases, responsibilities, engineering capacity, covered hours, response targets, and review cadence.

  2. Prepare access and context

    Complete the access review, inventory, diagnostic baseline, known-issue handover, and initial runbooks.

  3. Check readiness

    Validate alert routing and escalation contacts; confirm approvals, recovery priorities, and the coverage start date.

  4. Operate and review

    Begin the agreed coverage and maintenance work, then review findings and priorities on the selected cadence.

Review access and security

Plans & Pricing

Choose the scope your team needs.

Compare an engineering retainer with per-instance or cluster management. Confirm the work allowance, human coverage, and additional services alongside the indicative price.

View Managed DBA PlansDiscuss Your Scope

For a defined migration or tuning task, a project may be sufficient. For a single incident, review the separate support scope.

Explore project servicesSee per-incident support

FAQ

Common questions

Define your ongoing DBA coverage.

Share your database fleet, current ownership, and coverage needs. We can scope the operating relationship from there.

Discuss Your DBA Coverage