Same timezone · where the cloud regions actually are

SQL Server DBA services in Sydney

Your production database is probably already in Sydney even if your team is not — Azure Australia East and AWS ap-southeast-2 are both there. Remote SQL Server DBA cover on the same clock as your business, from $1,500 a month.

Free 20-point health check Call 1800 431 416

Sydney is where most Australian cloud databases physically live. Azure's Australia East region and AWS's ap-southeast-2 are both in Sydney, which means a large share of the country's Azure SQL databases, managed instances and RDS instances are sitting in a data centre a Sydney organisation could drive past — including plenty belonging to organisations in other states.

That matters more than it sounds. If your workload is in Australia East and your users are in Sydney, you have the best latency position in the country and performance problems are almost never about distance. It also means the decisions that do affect you are configuration decisions: instance sizing, storage tier, index design, how reporting shares the instance with transactional work. Those are DBA problems, and they are the same whether your consultant is in Sydney or Melbourne.

What we get called about in Sydney

The problems that come with being in the cloud region

Sydney estates skew cloud-first and financial-services-heavy, and both of those produce a recognisable set of database problems.

A cloud bill nobody can explain

Azure SQL and RDS make it trivial to solve a performance problem by increasing the tier. That works, monthly, forever. Most of the time the underlying cause is indexing or a query plan, and it is cheaper to fix than to rent around.

Managed does not mean administered

Azure SQL Managed Instance removes patching and a lot of infrastructure work. It does not tune queries, design indexes, test your restores or decide your recovery objective. Estates that moved expecting otherwise are a steady source of calls.

A hybrid estate nobody owns end to end

Part on-premises, part in Australia East, integrations crossing between them. The failure modes live in the seam, and the seam usually belongs to nobody.

Regulated workloads needing evidence

Sydney concentrates financial services, and with it APRA CPS 234 expectations and third-party reviews that ask who holds database credentials and in which country. We answer that in writing.

Single-region by accident

Everything in Australia East, including the backups. It is the default, it is rarely a decision anyone made, and it is worth knowing before an auditor asks rather than after.

An ageing version under a cloud veneer

SQL Server 2016 or 2017 lifted onto an Azure VM is still SQL Server 2016 or 2017. The infrastructure modernised; the end-of-support date did not move.

Why the timezone matters

Sydney and Melbourne run on the same clock

This is the one genuine advantage an eastern-states provider has for a Sydney client, and it is worth being concrete about what it buys.

NSW and Victoria share AEST and AEDT, including the daylight saving changeover dates — so there is never an offset to reason about
Your business hours are our business hours: a question at 9am is answered at 9am, not the following day
Change windows do not have to be negotiated across a time difference, which matters most for the overnight work where they are tightest
A 2am incident is 2am for the DBA who answers it, not a handover note written by someone finishing their afternoon
Nothing about remote support degrades at distance — Sydney to Melbourne is a secure connection, the same as a Sydney office to a Sydney data centre

Being straight about this

We are not based in Sydney

Onsys is a Melbourne practice. We support Sydney organisations remotely, on the same clock, and we would rather say that plainly than let a city page imply a local office.

Our office is at Level 1, 530 Little Collins Street, Melbourne VIC 3000, and our DBAs are in Australia
Database support is remote, which is how specialist database work is delivered everywhere — the alternative is an in-house DBA, not a local one
On-site attendance is available in the Melbourne metropolitan area as part of an engagement; elsewhere it is arranged and quoted case by case
What you get instead of proximity is a guaranteed response time, a named consultant who knows your estate, and published prices
If physical attendance matters more to you than any of that, we will say so rather than talk you out of it

Start with one Sydney instance

The free 20-point health check is read-only, needs no access to your environment, and gives you a written report within 3 business days — including when the answer is that your estate is in good shape.

Book the free health check

Published 9 October 2026

FAQ

Common questions

No. Onsys is a Melbourne practice and our DBAs are in Australia. Sydney clients are supported remotely on the same timezone, with a guaranteed response time at any hour. We would rather tell you that up front than have you find out on the first call. On-site attendance outside the Melbourne metropolitan area is arranged and quoted case by case.

Only in your favour. Australia East is the Sydney region, so if your users are in Sydney you already have the best latency position in the country. What we administer there is the same as anywhere else: performance, indexing, backup and restore verification, high availability, security and cost. Azure SQL Database, Managed Instance and SQL Server on Azure VMs are all in scope, as is Amazon RDS for SQL Server.

Because the managed platform covers infrastructure, not administration. Microsoft patches the platform and keeps it available. It does not tune your queries, design your indexes, test that your restores work, decide your recovery objective, or tell you that your reporting workload is competing with your transactional one. Those are the things that produce the bill and the incident.

Yes, and it is the default rather than an upgrade. Every login to a client database instance is made by an Onsys DBA based in Australia, and no offshore engineer holds credentials to a client database on any plan. We tell you which engineers hold access before you sign, and the terms go into the agreement.

Plan A is $1,500 per month excluding GST for up to 10 SQL Server instances — $150 per instance — with a guaranteed two-hour response at any hour and 10 professional service hours a month. Plan B is $3,000 and Plan C is $7,500 for larger and mixed-platform estates. Ad-hoc consultancy is $150 per hour with a four-hour minimum. Every figure is published.