Archive note
This page is preserved as part of the Harman Research editorial archive. Harman Research is the publisher-entity face for an independent portfolio of digital properties; it is not currently a consulting firm and is not soliciting consulting engagements. The content below is presented as historical reference to what "Remote DBA" meant in the late-1990s through late-2000s era.
What "Remote DBA" meant in the 1998–2010 era
In the late 1990s and 2000s, "Remote DBA" referred to a working pattern in which database administration tasks for production Oracle, SQL Server, and other RDBMS systems were performed off-site over dial-up, then VPN, then dedicated WAN links — rather than from a desk inside the customer's data center. The era predates the cloud-native operational model. Production databases ran on physical servers in customer-owned racks; remote operators connected through screen-sharing tools (PCAnywhere, Citrix, VNC, later GoToMeeting) and SSH terminals to handle backup verification, patching, performance triage, and incident response.
Operating systems of the era
The typical platform mix in this period included:
- Sun Solaris (versions 7, 8, 9, 10) on SPARC hardware
- IBM AIX on RS/6000 / pSeries
- Red Hat / Fedora / CentOS Linux as Linux took over from commercial Unix
- Windows Server 2000 / 2003 for SQL Server workloads
- IBM mainframe environments — VM, MVS, and VSE — still in production at large enterprises
Database management systems of the era
- Oracle — versions 8i, 9i, 10g, 11g; Oracle RAC 10g and 11g on Linux and Windows
- Microsoft SQL Server — 6.5, 7.0 (early-adopter cohort), 2000, 2005
- Less-traveled engines — Datacom/DB, Informix, Informix Illustra, Sybase
Why the pattern faded
Cloud platforms (AWS RDS, Azure SQL, Google Cloud SQL) and managed-database services collapsed much of the routine remote-DBA work into a vendor-managed control plane during the 2010s. The "Remote DBA" framing as a separately-marketed service category receded as DBA work migrated into platform engineering, SRE, and DevOps responsibilities at most enterprises. The archival reference here documents the era; the Harman Research entity is now a publisher of editorial content and does not provide DBA services.