DBA services for Canadian organisations,
from Vancouver to St. John's.
Who in Canada hires us.
- Mid-sized Canadian businesses running SQL Server, Oracle or PostgreSQL in production with no dedicated DBA, or with one person carrying every site.
- Organisations with operations in several provinces, where the Eastern office is asked to cover a Pacific site's night and nobody owns the gap.
- Software and SaaS companies in Canada whose product runs on PostgreSQL or SQL Server, with developers administering it between releases.
- Public-sector suppliers and regulated businesses that need a documented access model their privacy officer can sign off.
- 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.
Senior cover across every Canadian time zone.
One named DBA for every site
- Direct contact, no service desk
- Monthly report across all sites
- One fixed retainer, scope in writing
Maintenance in your night
- Maintenance windows staffed live
- Patching tested before production
- Restore tests run and timed
Handover in your morning, on call all day
- A written note on overnight work
- Incidents worked to root cause
- 24/7 on-call, reported monthly
Recovery you can show an auditor
- 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
Privacy sign-off, access, then a named DBA.
Agreements your privacy officer can sign
We sign your data processing agreement and security schedule before any access exists, and we document the access model so your privacy officer or security team can assess it against PIPEDA and the provincial rules that apply to you.
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 Canada, and nothing is copied out of it.
Health check, then one USD 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 across Canada.
| Your time zone | Standard time | Daylight time | What that means |
|---|---|---|---|
| Atlantic | 2 a.m. to 11 a.m. | 3 a.m. to noon | Overnight work staffed; most of your morning overlaps live |
| Eastern | 1 a.m. to 10 a.m. | 2 a.m. to 11 a.m. | Overnight work staffed; your morning overlaps for handover |
| Central | midnight to 9 a.m. | 1 a.m. to 10 a.m. | Overnight work staffed; early-morning overlap |
| Mountain | 11 p.m. to 8 a.m. | midnight to 9 a.m. | Your whole night is covered live; on call in your day |
| Pacific | 10 p.m. to 7 a.m. | 11 p.m. to 8 a.m. | Maintenance windows need no night shift; on call in your day |
Planned work goes into the change windows you set, which for most Canadian clients fall inside our ordinary working day.
PIPEDA, the provincial statutes, 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 Canadian buyers.
Questions Canadian clients ask.
Do you have DBAs in Canada?
No. Our engineers work from Johannesburg and Stellenbosch in South Africa, in UTC+2, and serve Canadian clients remotely inside the client's own environment. The time difference means your overnight maintenance happens in our working day, and the Eastern and Atlantic mornings overlap our afternoon for handover.
Can you work within PIPEDA and Quebec's Law 25?
Yes. The data stays in your environment in Canada; 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 officer's assessment.
Can one engineer cover sites in different provinces?
Yes. Remote cover does not care which province a server is in. The same named DBA looks after the Toronto, Calgary and Vancouver estates, with monitoring across all of them and one monthly report.
What hours are you actually working?
Our working day is 08:00 to 17:00 South African time, which is roughly 1 a.m. to 10 a.m. Eastern and 10 p.m. to 7 a.m. Pacific in standard time, one hour later in daylight time. Production support runs 24/7 on call under the retainer.
How is the retainer priced for a Canadian 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 Canadian 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 whichever 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.
