You can run SQL Server, MySQL, or PostgreSQL on a server in your office. Or you can run any of them in the cloud, where someone else manages the hardware, backups, updates, and availability.

For organizations without dedicated IT staff — which describes most Access shops — cloud hosting can be the difference between a successful migration and an abandoned one. Here is what is available, what it costs, and how to choose.

What “Cloud Database” Means

A cloud-hosted database is a database server that runs on someone else’s infrastructure. You get a connection string. You connect to it from Access (or any other application) the same way you would connect to a local server. The difference is that the provider handles:

You manage: - Creating databases, tables, and users - Permissions and security - Query performance and optimization - Your application (Access front-end)

Azure SQL Database

What it is: Microsoft’s managed SQL Server in the cloud.

Why it fits Access replacement: This is the path of least resistance from Access. Same SQL dialect, same ODBC drivers, same management tools (SSMS). If your Access application uses SQL Server-specific features, they work on Azure SQL.

Pricing (Basic tier): Starting around $5/month for 2GB of storage. The General Purpose tier (more performance, up to 4TB) starts around $30-50/month. Pricing depends on compute power and storage.

Setup: Create an Azure account, provision an Azure SQL Database through the portal, configure the firewall to allow connections from your office IP, and connect with a standard ODBC connection string.

Pros: - Identical to SQL Server for Access compatibility - Automated backups with point-in-time restore - Scales up without migration - Integrates with other Microsoft services

Cons: - Monthly ongoing cost - Requires internet connectivity (if the internet goes down, you lose database access) - Latency is higher than a local server (typically 10-50ms vs. <1ms) - Data egress costs if you move large amounts of data out

Amazon RDS

What it is: Amazon’s managed database service. Supports MySQL, MariaDB, PostgreSQL, and SQL Server.

Why it fits: Flexibility. You can choose MySQL, MariaDB, PostgreSQL, or SQL Server based on your preferences, and Amazon handles the infrastructure for all of them.

Pricing: Starts around $15-25/month for the smallest instances (db.t3.micro or db.t4g.micro). Storage is charged separately ({{content}}.115/GB/month for general purpose SSD). A typical Access replacement workload might cost $20-40/month.

Setup: Create an AWS account, launch an RDS instance through the AWS console, configure the security group (firewall), and connect via ODBC.

Pros: - Supports multiple database engines - Automated backups and maintenance - Multi-AZ deployment for high availability - Extensive documentation

Cons: - AWS console has a steep learning curve - Pricing is complex with many variables - Requires internet connectivity - May be overkill for simple Access replacement

Google Cloud SQL

What it is: Google’s managed database service. Supports MySQL, PostgreSQL, and SQL Server.

Pricing: Similar to AWS RDS. Starts around $10-25/month for basic instances.

Pros: Good integration with Google Workspace if your organization uses it. Straightforward pricing.

Cons: Smaller community than AWS or Azure. Less documentation specifically about Access migration.

DigitalOcean Managed Databases

What it is: A simpler, more affordable managed database service. Supports MySQL and PostgreSQL.

Pricing: Starts at $15/month for a basic MySQL or PostgreSQL instance with 1GB RAM, 10GB storage, and a single node.

Pros: - Simpler pricing and interface than AWS or Azure - Good documentation - Lower cost for basic workloads

Cons: - No SQL Server option - Fewer features than AWS or Azure - Less mature high-availability features

Running Your Own Cloud Server

Instead of a managed database, you can rent a basic cloud server (VM) and install the database yourself:

On this server, you install MySQL, MariaDB, or PostgreSQL just as you would on a local machine.

Pros: - Cheapest option - Full control over configuration - No database-specific vendor lock-in

Cons: - You manage everything: OS updates, database updates, backups, security, monitoring - Essentially the same admin burden as a local server, just in a different location - If you don’t know what you’re doing, you may create security vulnerabilities

Recommendation: Unless you have server administration experience, use a managed database service rather than a self-managed VM.

The Latency Question

The biggest concern about cloud databases for Access replacement is latency. Access linked tables make frequent ODBC round trips — every form load, every record save, every combo box population is a network call.

On a local server, these round trips take less than 1 millisecond. On a cloud database, they take 10-50 milliseconds. That difference multiplies across dozens of ODBC calls when a form opens.

The practical impact: Simple forms with a few controls may feel slightly slower. Complex forms with multiple subforms and DLookup calls can feel significantly slower. Reports that make many small queries are affected more than reports that make one large query.

Mitigations: - Optimize forms to reduce ODBC round trips (fewer subforms, no DLookup, filtered record sources) - Use pass-through queries for complex operations - Choose a cloud region close to your office to minimize latency - If some users are remote/VPN already, they may not notice a difference

How to Decide

Choose cloud if: - You do not have a server or someone to manage one - Your team is remote or distributed across locations - You want backups and maintenance handled for you - You are okay with a monthly operating cost - Your Access application has been optimized to minimize ODBC round trips

Choose local server if: - You already have a server and someone who manages it - Latency is critical (complex forms with many subforms and lookups) - Internet reliability is a concern for your location - You want zero ongoing costs after initial setup - Data residency requirements prevent cloud hosting

The middle ground: Start with a local SQL Server Express installation. It is free, it solves your Access problems, and it requires minimal new skills. If you later want cloud benefits (remote access, managed backups, high availability), you can migrate the SQL Server database to Azure SQL Database with minimal application changes.

Cost Comparison

For a typical Access replacement (5GB database, 15 users):

Option Monthly Cost Your Effort
SQL Server Express (local) {{content}} High (you manage everything)
Azure SQL Basic $5-15 Low (managed service)
Azure SQL General Purpose $30-60 Low (managed service)
AWS RDS (MySQL/PostgreSQL) $20-40 Low (managed service)
DigitalOcean Managed DB $15-30 Low (managed service)
Self-managed cloud VM $5-15 High (you manage everything)

The managed services cost more per month but save significant IT labor. For organizations without a DBA, the managed service cost is almost always justified.