DBA services for Australian organisations.
We work your afternoon and your night.
Who in Australia hires us.
- Mid-sized Australian businesses running SQL Server, Oracle or PostgreSQL in production with no dedicated DBA, or with a single DBA and no cover for leave and nights.
- IT leaders who want a named engineer with direct contact details rather than a managed-service queue, and who would rather not staff an overnight roster.
- Software and SaaS companies in Australia whose product runs on PostgreSQL or SQL Server, with developers administering it between releases.
- Organisations with sites in more than one state or in New Zealand, where one estate spans three clocks.
- Estates on SQL Server 2016 or 2017, Oracle 19c or PostgreSQL 14 with the end-of-support date known and the upgrade not yet planned.
Cover that starts in your afternoon and runs through your night.
Your afternoon: live handover
- Direct contact with the named DBA
- Incidents worked to root cause
- Changes agreed before your team leaves
Your evening and overnight: watched, not hoped for
- Overnight batch and backups monitored live
- Maintenance windows staffed by senior DBAs
- Restore tests run and timed overnight
Your morning: a note, then on call
- A morning note on overnight work
- 24/7 on-call under one retainer
- Response commitments reported monthly
Backups proven by restore
- Scheduled, timed restore tests
- Recovery objectives written down
- Retention aligned to the business
Availability and disaster recovery
- Failover rehearsed on a schedule
- DR site kept in step
- Change windows with a rollback path
Performance, capacity and lifecycle
- Wait, plan and blocking analysis
- Growth tracked against real usage
- End-of-support dates planned for
Agreement, access, then a named DBA.
Agreements before access
We sign your data processing agreement and security schedule before any access exists, and we document the access model so your security or privacy team can assess it against the Australian Privacy Principles.
Access through your own path
Access runs through your VPN, bastion host or jump server, with named accounts and multi-factor authentication. The work happens inside your environment, in your Australian region, and nothing is copied out of it.
Health check, then one retainer
A senior DBA assesses the estate through that access and writes a prioritised list. Ongoing cover then runs under one fixed monthly retainer quoted in USD, with response commitments we report against.
Where our day falls in the Australian day.
| Where you are | Standard time | Daylight time | What that means |
|---|---|---|---|
| Sydney, Melbourne, Canberra, Hobart (AEST / AEDT) | 16:00 to 01:00 | 17:00 to 02:00 | Afternoon handover live; overnight batch and backups watched |
| Brisbane (AEST, no daylight saving) | 16:00 to 01:00 | 16:00 to 01:00 | Afternoon handover live; overnight batch and backups watched |
| Adelaide (ACST / ACDT) | 15:30 to 00:30 | 16:30 to 01:30 | Afternoon handover live; overnight watched |
| Perth (AWST, no daylight saving) | 14:00 to 23:00 | 14:00 to 23:00 | Most of your afternoon overlaps live; evening watched; on call after |
Planned work such as upgrades, failover tests and index rebuilds is scheduled in your change windows, which for most Australian clients fall inside our ordinary working day.
The Australian Privacy Principles and where the data stays.
- Named accounts and multi-factor authentication, through your VPN, bastion host or jump server
- Access scoped to the work, with sessions your team can audit
- Data processing agreement and security schedule signed before any access
- No personal information copied, exported or held outside your environment
SQL Server, Oracle and PostgreSQL, under one retainer.
- SQL Server 2016: extended support ended 14 July 2026. What that means.
- SQL Server 2017: extended support ends 12 October 2027. The options, ranked.
- SQL Server 2019: extended support ends 8 January 2030. Dates and planning.
- Oracle Database 19c: Premier Support ends 31 December 2029. The real dates.
- PostgreSQL 14: final minor release 12 November 2026. Upgrade paths.
Work we can show Australian buyers.
Questions Australian clients ask.
Do you have DBAs in Australia?
No. Our engineers work from Johannesburg and Stellenbosch in South Africa, in UTC+2, and serve Australian clients remotely inside the client's own environment. Our working day begins in your afternoon and runs through your night, which is exactly when the batch, the backups and the maintenance windows need someone awake.
Can you work within the Australian Privacy Principles?
Yes. The data stays in your environment and your Australian region; access is through named accounts with multi-factor authentication over your own VPN or bastion host; and we sign your data processing agreement and security schedule before access exists, with the access model documented for your privacy team.
Who watches the overnight batch?
A senior DBA who is at work. Our 08:00 to 17:00 is 16:00 to 01:00 in Sydney in standard time, so the overnight batch, backups and maintenance run while an engineer is watching them, and your team arrives to a written note on what happened.
What about our morning, when you are asleep?
Production support runs 24/7 on call under the retainer, with the response commitments written into the scope and reported against monthly. It is the same engineer, or the same small group, who knows your estate, not a service desk.
How is the retainer priced for an Australian company?
As one fixed monthly figure quoted in USD, with the scope, the platforms covered and the response commitments written down. No per-ticket billing and no separate after-hours charge. The figure depends on the estate, so it follows the health check.
Do you support databases on AWS and Azure in Australian regions?
Yes. We administer SQL Server, Oracle and PostgreSQL on premises, on virtual machines and on the managed database services of AWS and Azure, in the region your residency requirements place them, and we plan and run moves between them. Moving SQL Server to Azure
How do we start?
Use the form on this page or email expert@radixtrie.com. A senior DBA replies directly, and the first conversation is about understanding your estate, not selling to it.
