Skip to main content
Cloud Intelligence Solutions

Database Solutions

Database Support Services

Specialist Help for Database Issues

Database Support Services give your in-house IT or DBA team specialist help with database incidents, failed changes, performance concerns, and configuration questions, while your team continues to run the databases. Covered platforms, versions, environments, access, hours, and escalation arrangements are set out in the support agreement before support starts.

What We Deliver

Where We Make the Difference

Most database work is handled well by the team that runs it. Support is for the issues that need more specialist investigation. We gather evidence, investigate database-side causes, and recommend actions, and where the support agreement includes implementation, we carry out approved changes. Some issues trace to applications, infrastructure, or vendor software, and some cannot be resolved quickly or fully, so findings and open questions are documented either way.

01

Evidence-Based Investigation

We review logs, error messages, wait and resource data, execution plans, configuration, and recent changes to narrow down database-side causes. Investigation depends on the access and diagnostic evidence available, and gaps are recorded.

02

Agreed Hours and Escalation

The support agreement defines covered hours, severity levels, how issues are raised, and the contacts on each side. It distinguishes acknowledgment, the start of investigation, escalation, and any resolution commitments, and states any applicable targets.

03

Approved Changes and Recovery

Recommended changes include their risks, testing needs, recovery options, and limitations. Who implements them is agreed within the support scope. Any production change follows your approval process.

04

Shared Responsibilities

Your team, application owners, infrastructure providers, and software vendors keep their own responsibilities. Where a vendor case is needed, it is opened under your vendor support entitlements by your team or a contact you authorize, and vendor response is outside our control.

Our Approach

How We Deliver Database Support Services

  1. Step 1: Agree the Scope

    We agree the platforms, versions, environments, and databases covered, support hours, severity definitions, how issues are raised, escalation contacts on each side, and what falls outside support.

  2. Step 2: Onboard and Set Up Access

    Your organization grants access through its approval process. We document the environment details needed for support and confirm we can reach diagnostic sources such as logs and performance data, recording any gaps.

  3. Step 3: Investigate and Advise

    When an issue is raised, it is acknowledged, assessed for severity, and investigated with the evidence available. We share findings and recommended changes, and any production change requires your approval. Our team implements approved changes only where the support agreement includes that work. We escalate to your contacts as agreed. Vendor escalation requires your authorization, applicable support entitlements, and agreement on who manages the case.

  4. Step 4: Document Findings and Next Steps

    We maintain an issue record covering actions, findings, root cause where determined, and unresolved questions. Closure or handover is agreed with your team, with outstanding actions and owners documented. Work outside the support scope is agreed separately.

FAQ

Common Questions

Something we did not cover? Ask us directly.

How is Database Support different from Remote DBA or DBA staffing?

Database Support gives your team specialist help with database issues while your team runs the databases. With Remote DBA, our team carries out agreed administration tasks under a service agreement, while your organization keeps ownership and change approval. DBA Staffing Services place a DBA who works under your direction. Ongoing administration, monitoring setup, and project delivery require explicitly agreed scope and responsibilities.

What happens when we raise an issue?

During covered hours, the issue is acknowledged, assessed for severity, and investigated on the database side. The support agreement distinguishes acknowledgment, the start of investigation, escalation, and any resolution commitments, and defines any applicable targets and how they are measured. Support is provided during the hours set in the agreement. Resolution may depend on applications, infrastructure, vendors, or approvals.

Do you guarantee a fix or a root cause?

No. We investigate with the access and evidence available and recommend actions with their expected effect and risk. Some issues are resolved, some are mitigated, and some trace to applications, infrastructure, or vendor software outside our control. Root cause is documented where it can be determined, and unresolved findings are recorded with suggested next steps. Further risk reduction or better visibility may require separately scoped work, such as Database Tuning or Database Monitoring.

How are access and production changes handled?

Your organization grants, reviews, and revokes our access. We ask for named accounts with permissions limited to support tasks where your platforms allow it, and diagnostic work starts with read access where possible. Recommended changes state their recovery options and limitations, and any production change requires your approval. Our team implements approved changes only where the support agreement includes that work. You keep ownership of your databases and data.

Can support cover upgrades, migrations, or other planned work?

Support can include advice on planned changes where the agreement includes it. Whether implementation or follow-up fixes are included depends on the agreed scope. Larger activities, such as version upgrades, migrations, tuning projects, or recovery exercises, require explicit scope and may be delivered through Database Upgrades or Complex Database Migrations.

Keep Exploring

View All

Next Step

Tell us where your data, applications, or workflows are slowing your team down. We'll discuss your priorities and identify a practical starting point.