Expert guide

Access vs Dataverse vs SQL Server: Choosing a Back End

Where your data should live when the Access file starts to strain

Free Cost Audit

Call us at +1 (385) 386-3860

Short answer: keep an Access back end for small teams on one network with modest data. Move to SQL Server (Express is free up to 10 GB per database) or Azure SQL when you need more data, more users, remote access or stronger security, while keeping Access forms. Choose Dataverse when the future is the Power Platform: model-driven Power Apps, Dynamics 365, built-in roles and auditing, and you accept per-user licensing. Our Access to SQL Server and modernisation projects start with this decision.

When an Access database becomes important, the back end is the first thing to outgrow: the file nears 2 GB, corruption appears over Wi-Fi or VPN, remote staff cannot connect, or security reviews flag a shared file holding customer data. The question is not whether to keep Access forms, but where the data should live. The three realistic options are very different in cost and capability.

Comparison

AspectAccess back endSQL Server / Azure SQLDataverse
TypeFile-based databaseClient-server relational engineManaged cloud data platform
Size2 GB per file10 GB per DB (Express); far more on paid tiersCapacity by licence; extra storage charged
UsersSmall team on a LANHundreds+Licensed users
Remote accessPoor over VPN; use remote desktopGood (VPN, private network or Azure)Native, cloud
SecurityFolder permissionsLogins, roles, encryption, auditingRole-based, row and field security, auditing
Business logicIn Access (VBA, queries)Views, procedures, triggersBusiness rules, plug-ins, Power Automate
Access front endNativeLinked tables via ODBCLinked tables via connector
Power AppsNot suitablePremium connectorNative
Typical costMinimalFree (Express) to monthly (Azure/Standard)Per-user licences + capacity

Choose an Access Back End When

  • Fewer than roughly 10–15 concurrent users on a reliable wired network.

  • Data comfortably under 1 GB and growing slowly.

  • No remote users, or remote users via remote desktop.

  • Data sensitivity is moderate and folder permissions are acceptable.

Make sure it is split and backed up; see how to split an Access database.

Choose SQL Server or Azure SQL When

  • The back end is approaching the 2 GB limit or growing quickly.

  • Corruption or locking problems come from many users or unreliable networks.

  • Remote users need direct access, or other tools (Power BI, Excel, web apps) need the data.

  • You need proper logins, auditing and backups with point-in-time restore.

  • You want to keep Access forms and reports with minimal retraining.

This is the most common upgrade path for Access systems. The forms stay; heavy queries move to server views. See AI-assisted Access to SQL Server migration, the 2 GB limit and ODBC errors.

Choose Dataverse When

  • New apps will be built in Power Apps (especially model-driven apps).

  • The organisation uses or plans Dynamics 365.

  • You need role-based security down to rows and fields without building it yourself.

  • Users already have, or will be licensed for, Power Apps.

  • IT wants data governed inside Microsoft's Power Platform environments.

Access can link to Dataverse during a transition, so office users keep Access screens while new Power Apps are built. Weigh licences carefully; the trade-offs are in Access vs Power Apps.

Migration Considerations

IssueTo SQL ServerTo Dataverse
Data typesClose mapping; check Yes/No, dates, currencyDifferent column types; choices, lookups, file and image columns
Multivalued and attachment fieldsMust be converted firstMust be converted first
QueriesRun linked, heavy ones become viewsLogic often moves to views, flows or app formulas
VBA in formsMostly keeps working with fixesKeeps working in Access; not reusable in Power Apps
ReportsAccess reports unchangedAccess reports work; Power BI for cloud reporting

Preparation steps apply to both: replace multivalued fields, run data quality checks, and document the database before moving anything.

A Simple Decision Rule

  • Problems are size, reliability or remote access, and Access forms work well: SQL Server or Azure SQL.

  • Future is Power Apps and Dynamics, with users licensed: Dataverse.

  • Small, stable, on-site team: keep Access, split and backed up.

  • Not sure: get a written assessment comparing total cost over three to five years.

FAQ

Access vs Dataverse vs SQL Server FAQ

Choosing where your data lives

An Access back end is a file-based database for small teams on one network. SQL Server (including Azure SQL) is a full client-server database engine for larger data, more users and remote access. Dataverse is Microsoft's managed cloud data platform for the Power Platform, with built-in security roles, auditing and business rules, licensed per user through Power Apps and Dynamics 365.

Yes. Access can link to Dataverse tables, so Access forms can work with data that Power Apps also uses. Performance and data-type behaviour differ from SQL Server, and users need appropriate Power Platform licences to access Dataverse data.

For many, yes. SQL Server Express is free, supports databases up to 10 GB each, and handles typical small-business workloads with dozens of users. Larger databases, high availability or advanced features need Standard edition or Azure SQL.

An Access back end has almost no running cost. SQL Server Express is free software but needs a server or VM to run on; Azure SQL has a monthly cost based on size and performance. Dataverse cost comes mainly from per-user Power Apps licences and storage beyond included capacity.

Both Dataverse and SQL work with Power Apps. Dataverse integrates most smoothly with model-driven apps, security and Dynamics 365. SQL is often cheaper for data accessed by many users through Access or other tools, but Power Apps connecting to SQL uses premium connectors that require licences.