Remote DBA is an ongoing service in which our team carries out agreed database administration for the platforms, environments, and tasks in scope. It supports organizations that need external help with defined operational responsibilities. Coverage hours, responsibilities, access, escalation, and change approval are agreed before the service starts.
Routine database care often slips when no one is assigned to it. We take on the administration tasks agreed in scope, work through your access and change processes, and report what was done and what needs attention. Regular maintenance and review can reduce some risks and surface issues earlier, but cannot prevent every failure, so escalation and recovery arrangements are agreed in advance.
01
Scheduled Administration
Health checks, backup job review, database software patching where included and approved, index and statistics maintenance, and capacity reviews run on an agreed schedule for the databases in scope. A completed backup job does not prove a restore will succeed. Whether restore testing is included, and its scope and frequency, is defined in the agreement.
02
Alert Review and Incident Response
During covered hours, we acknowledge alerts and requests, investigate database-side causes, and work with your team and vendors toward restoring service. Actions and findings are recorded, with root cause documented where it can be determined. Alert review depends on monitoring that is in place and included in scope.
03
Controlled Access and Change
Your organization grants, reviews, and revokes our access. We ask for named accounts with permissions limited to agreed tasks where your platforms support it, and privileged actions and production changes follow your approval process. We agree the access controls and activity logging available in your environment, and document any gaps and required actions before operational work starts.
04
Defined Scope and Responsibilities
The agreement lists covered platforms, versions, environments, tasks, and hours, along with what your team, vendors, and infrastructure providers remain responsible for. Work outside that scope, such as upgrades or migrations, is identified and scoped separately.
Our Approach
How We Deliver Remote DBA Services
01
Step 1: Onboard and Assess
We set up access through your approval process, document the databases, backups, maintenance jobs, and existing monitoring in scope, and record a health baseline. Known access or visibility gaps are listed, along with what cannot be covered until they are resolved.
02
Step 2: Agree the Runbook
Together we define the tasks each side owns, coverage hours and time zone, severity levels, escalation contacts, change approval and emergency authority, incident ownership, and how we communicate during an incident.
03
Step 3: Operate Within the Agreed Scope
Our DBAs carry out scheduled maintenance, review alerts and handle requests during covered hours, and make changes through your process, with work performed recorded. If monitoring needs to be set up or extended, that work is scoped during onboarding or as a separate engagement.
04
Step 4: Report and Review
Regular reports cover work completed, incidents, health and capacity trends, open gaps, and upcoming risks such as end-of-support dates. Scope and coverage are reviewed when your estate or priorities change.
Your service agreement defines the offered coverage hours and time zone, holiday arrangements, covered databases, and handling of alerts or requests outside those hours. The runbook records the relevant contacts and escalation arrangements. Coverage applies only during the hours set in the agreement.
What happens when an alert fires or you report an issue?
During covered hours, the alert or request is acknowledged, assessed for severity, and investigated on the database side. The agreement distinguishes acknowledgment, the start of investigation, escalation, and any resolution commitments. It defines any applicable targets and how they are measured. Resolution may depend on applications, infrastructure, vendors, or approvals. Alerts come from the monitoring in place; if coverage is missing, setup can be scoped through Database Monitoring.
How is access controlled, and who approves changes?
Your organization grants, reviews, and revokes our access. We ask for named accounts with permissions limited to the agreed tasks where your platforms support it, and use the access methods you require. Privileged actions and production changes follow your approval process, and the runbook records who can approve emergency actions and within what limits. We agree the access controls and activity logging available in your environment, and document any gaps and required actions before operational work starts. You keep ownership of your databases and data.
What is included, and what is scoped separately?
Routine administration for the databases in scope, such as scheduled maintenance, backup job review, database software patching where included and approved, and alert response during covered hours, is included as agreed. Version upgrades, migrations, restore and recovery exercises, performance tuning projects, and new builds are scoped separately unless your agreement includes them. These can be delivered through services such as Database Upgrades, Complex Database Migrations, and Database Tuning.
How is Remote DBA different from Database Support or DBA staffing?
Remote DBA covers agreed ongoing administration under a service agreement. Database Support Services give your own team specialist help with incidents and escalations while your team runs the databases. DBA Staffing Services place a DBA who works under your direction. Scope can start with selected databases and expand by agreement.