24/7 cover · From $1,500/month · No lock-in

Remote database support in Australia

Remote database support is the ongoing monitoring, patching, tuning and recovery of your databases by an external DBA team working over a secure connection, instead of employing a full-time in-house DBA. Onsys provides it 24 hours a day to Australian organisations running SQL Server, Oracle, PostgreSQL and MySQL, with first response in one to two hours and no minimum contract term.

What is included

What does a remote DBA service actually include?

Remote database support covers the work an in-house DBA would do, delivered by a team over a secure connection — without the headcount, the leave cover or the single point of failure.

Monitoring and alerting

Continuous checks on availability, space, jobs, replication health and error logs, with alerts routed to an engineer rather than an inbox nobody reads.

Incident response

A senior DBA on the problem within the response time your plan specifies, 24 hours a day, including the 2am ones.

Backup and recovery

Backups verified, restores actually tested, and recovery objectives documented against what the configuration can really deliver.

Patching and upgrades

Cumulative updates and security patches applied in your change window, with a tested rollback.

Performance tuning

Query, index and configuration work using the monthly professional service hours included in every plan.

Reporting and advice

A monthly health report and a named consultant who knows your estate, rather than whoever picks up the ticket.

Platforms

What database platforms do you support?

Four production platforms plus their managed cloud equivalents, supported by engineers certified on each.

Microsoft

  • SQL Server 2008–2022
  • Azure SQL Database
  • Azure SQL Managed Instance
  • SQL Server on Azure VM
  • Always On availability groups
  • SSIS · SSRS · SSAS

Oracle

  • Oracle 10g – 23ai
  • Oracle RAC
  • Oracle Data Guard
  • Oracle Cloud (OCI)
  • RMAN & recovery
  • Enterprise Manager

Open source

  • PostgreSQL
  • EDB Postgres
  • MySQL & MariaDB
  • MongoDB
  • Streaming replication
  • Group replication
Onboarding

How long does onboarding take?

Two weeks from signature to full coverage is typical. Nothing is charged until coverage actually starts.

Week 1 — discovery

We inventory the estate, run the 20-point check on the critical instances, and agree the escalation path and change process.

Week 1 — access

Secure connectivity is established using your preferred method, with named accounts and logged access. No shared credentials.

Week 2 — monitoring

Alerting is configured and tuned against your thresholds so you are not paged for noise.

Week 2 — go live

Coverage starts, the first monthly report is scheduled, and you get the direct number for your named consultant.

Speak with a senior DBA today

A 30-minute call with the consultant who would run your estate — not a salesperson, and not a form response.

Book a free consultation

Published Last reviewed

FAQ

Common questions

Remote database support is the ongoing monitoring, patching, tuning and recovery of your databases by an external DBA team working over a secure connection. It replaces or supplements an in-house DBA, and covers the same work: availability monitoring, incident response, backup verification, patching, performance tuning and capacity planning.

Remote DBA support in Australia typically costs between $1,000 and $8,000 per month depending on instance count and coverage hours. Onsys plans start at $1,500 per month ex-GST for up to 10 SQL Server instances with 24/7 coverage, and $7,500 per month for multi-platform estates up to 50 TB. Ad-hoc senior DBA work is $140 per hour, billed in 30-minute increments, with no minimum term.

It is, provided the access is named, least-privilege, logged and revocable — and you should require all four from any provider. Onsys uses individually named accounts rather than shared credentials, connects over your preferred secure channel, and every session is logged and auditable. We document which engineers hold access before you sign, and access is revoked the day an engagement ends. If your policy prohibits external logins entirely, we work screen-shared with your own staff driving.

True 24/7/365 database cover needs five to seven DBAs, because one person cannot cover nights, weekends, leave and resignation. Below roughly three full-time DBAs of genuine workload, a managed service is almost always cheaper and more resilient than hiring. Above that, a hybrid is common: in-house staff own the application-facing work and an external team carries after-hours and specialist platforms.

You call the 24/7 number and reach an on-call senior DBA, not a first-line triage queue. On a monthly plan the first response is guaranteed within one to two hours depending on tier, and triage starts on the phone. We hold your runbooks and access already, so no time is lost establishing who you are or how to reach the estate.

Australian-based senior consultants lead every engagement and hold the client relationship from Melbourne. Round-the-clock coverage is delivered together with our Colombo delivery centre. We tell you exactly which engineers hold access to your environment before you sign, and it is written into the agreement. If you require Australian-resident-only access for regulatory reasons, say so during scoping and we will tell you plainly whether we can meet it.

Two weeks from signature to full coverage is typical: one week for discovery, access and runbooks, one week for monitoring configuration and tuning. Nothing is billed until coverage actually starts.

No. Monthly plans run on a rolling basis with no minimum term and no exit fee. If the service is not worth what it costs, you should be able to stop paying for it.