ACST · the half-hour nobody schedules for

SQL Server DBA services in Adelaide

South Australia runs half an hour behind the eastern states, which is just small enough that everyone ignores it and just large enough to put a job in the wrong window. Remote SQL Server DBA cover scheduled in ACST, from $1,500 a month.

Free 20-point health check Call 1800 431 416

South Australia is half an hour behind the eastern states — ACST at UTC+9:30, ACDT at UTC+10:30. It is the offset most likely to be quietly assumed away, because half an hour feels like a rounding error until a maintenance job starts thirty minutes into a batch run, or an agreed 11pm window turns out to have meant 11pm somewhere else.

Adelaide estates also tend to carry a particular obligation profile. South Australia has a concentrated defence and defence-supply-chain sector, and organisations in it frequently have to answer security questions that go beyond the usual — specifically about who holds credentials to systems, where those people are, and whether any of that can be committed contractually rather than asserted on a website.

Both of those are answerable. They just have to be asked about rather than assumed.

The half hour

Scheduling that accounts for ACST

A thirty-minute offset is not technically difficult. It is just the one people round away, which is why it is worth being explicit about.

ACST is UTC+9:30 and ACDT is UTC+10:30 — half an hour behind the eastern states year-round, including during daylight saving
Every change window, maintenance schedule and report time is written with its timezone attached rather than as a bare clock time
Where an Adelaide database replicates to or from an eastern site, the overlap between the two maintenance windows is worked out in both offsets rather than assumed to be the same
SQL Agent job schedules are checked against the server timezone, which in cross-state estates is frequently not the timezone the business is operating in
SLA response times are measured in elapsed time, so the half hour has no effect on how quickly a DBA reaches your problem
South Australia and the eastern states change daylight saving on the same dates, so unlike Queensland the offset is constant — which is easy to plan for once it is written down

What we get called about in South Australia

Defence supply chain, health and mid-market estates

Adelaide estates are frequently smaller than their obligations, which is a specific and solvable problem.

Security questions beyond your size

A defence prime or a government customer asks a supplier of forty people the same supply-chain security questions it asks an enterprise. Answering "who holds database credentials and where are they" in writing is usually the sticking point.

Patch currency as a contract condition

The ACSC Essential Eight expects vendor-supported, patched software, and it increasingly appears as a condition rather than a recommendation. An out-of-support SQL Server version is the control that fails first.

No DBA, and no plan to hire one

The common mid-market pattern: a capable systems administrator running a production estate competently until something needs a specialist, with no escalation path when it does.

A DR plan nobody has tested

Disaster recovery that exists on paper because testing it would mean an outage, and the test keeps being deferred. We have rebuilt exactly this for clients so the DR test runs while production stays open.

Jobs running in the wrong window

Server timezone, application timezone and business timezone disagreeing, so a maintenance job lands inside a batch run. Small, embarrassing, and genuinely common in cross-state estates.

Health and research databases

Adelaide has a dense health and research sector, where identified data frequently sits in databases administered by whoever built them. A good place to start an access review.

Being straight about this

We are not based in Adelaide

Onsys is a Melbourne practice. We support South Australian organisations remotely, scheduled in ACST, with the access terms available in writing for the supply-chain reviews that sector tends to attract.

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 Adelaide instance

The free 20-point health check reports the version and patch level of the instance in writing, which is usually the first thing a supply-chain security review asks for — and it needs no access to your environment.

Book the free health check

Published 9 October 2026

FAQ

Common questions

No. Onsys is a Melbourne practice and our DBAs are in Australia. South Australian clients are supported remotely, scheduled in ACST, with a guaranteed response time at any hour. On-site attendance outside the Melbourne metropolitan area is arranged and quoted case by case.

Yes, and we encourage it — a commitment that lives only on a website is a marketing claim. Database access is held by Onsys DBAs based in Australia only, no offshore engineer holds credentials to a client database on any plan, access is through named accounts with session logging, and it is revoked the day an engagement ends. Raise it during scoping and all of that is written into the agreement you sign.

We can answer the parts that concern us: who holds credentials to your database environment, where those people are, how access is granted and logged, and how it is revoked. We provide the current access list on request at any point in the engagement. We are a service provider rather than your assurance function — we supply the evidence and your team makes the attestation.

It causes scheduling mistakes rather than technical ones. The two we see most are a maintenance job starting thirty minutes into a batch run, and a SQL Agent schedule set against a server timezone that is not the one the business operates in. Both are trivial to fix once someone has written down which clock each system is on, which is part of the initial assessment.

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.