How do you choose the right SQL Server edition for an ERP environment?

The choice between SQL Server Standard and Enterprise for ERP environments is not a cosmetic one. The price difference is roughly a factor of four per core, and the technical limitations of Standard directly affect scalability, availability, and compliance. For an ERP system such as Microsoft Dynamics 365 Business Central, SAP Business One, Exact Globe, AFAS Profit, or Unit4 ERP, the edition choice determines both performance and annual IT costs. In this article, you will read which editions exist, which decision factors matter for an ERP workload, and which edition fits which scenario.

Why the SQL Server edition matters for an ERP environment

An ERP database has three characteristics that make the edition choice more critical than for ordinary line-of-business applications. First, an ERP database almost always grows linearly over time: financial transactions, inventory changes, and order lines are rarely deleted. A database of 50 GB at go-live can grow to 500 GB or more within five years.

Second, an ERP system is almost always business-critical. Downtime translates directly into halted warehouses, unprocessed orders, and missed invoicing. That places demands on high availability, and therefore on the capabilities of Always On availability groups.

Third, modern ERPs are increasingly combined with BI reporting, data warehouses, and external integrations (EDI, e-commerce, WMS). That mixed workload puts a fundamentally different load on a SQL instance than a pure OLTP database.

The three SQL Server editions at a glance

SQL Server 2025 has three commercial editions that are relevant for on-premises ERP implementations. The table below shows the main differences. The limits in this table apply to SQL Server 2025; for earlier versions, the limits for Standard are lower (SQL Server 2022 and older: 24 cores and 128 GB RAM).

Source: Editions and Supported Features of SQL Server 2025 (Microsoft Learn). Developer edition is functionally identical to Enterprise but intended exclusively for development and test environments.

For a production ERP environment, Express is not a practical option. The combination of a 1.4 GB buffer pool and the absence of high-availability options makes Express unsuitable for anything other than a demo or development installation, even though the maximum database size in SQL Server 2025 has been increased to 50 GB. In practice, the choice is therefore almost always between Standard and Enterprise.

Six decision factors for choosing the right edition for an ERP

The choice between Standard and Enterprise rarely depends on a single criterion. The following six factors help structure the decision.

1. Database size and expected growth

Both editions support databases up to 524 petabytes, so the hard limit is not relevant in practice. What size does determine, however, is how much memory you need to keep a workable portion of the database in the buffer pool. A rule of thumb for OLTP ERP: 10 to 15 percent of the database size as buffer pool. For a 500 GB database, that means roughly 50 to 75 GB RAM, well within Standard's 256 GB. Above 1.5 TB of database size, Enterprise becomes more attractive, partly because of partitioning.

2. Number of concurrent users and workload type

For an ERP with 100 to 250 concurrent users, Standard is generally sufficient. Above 500 concurrent users, you start to see the parallelism limitations of Standard (batch mode DOP maximum 2) reflected in reporting queries. If you combine OLTP with heavy BI queries on the same instance, Enterprise is worth it because of the advanced columnstore optimizations and higher DOP.

3. Uptime and availability requirements

Since SQL Server 2016, Standard supports basic availability groups: two nodes, one database per group, no readable secondary. That is sufficient for organizations with an RTO (recovery time objective) of several minutes to one hour. If you want to replicate multiple databases synchronously, readable secondaries for reporting, or three or more replicas (for example for a DR site alongside a local HA setup), then you need Enterprise.

4. Compliance and encryption

Transparent Data Encryption (TDE) encrypts the data files on disk without requiring changes to the application. For organizations that, under GDPR, NIS2, or sector-specific standards (NEN 7510 in healthcare, DORA in the financial sector), must implement data-at-rest encryption, this is a hard requirement. TDE is available only in Enterprise. Alternatives at the Standard level, such as column-level encryption or BitLocker on the volume, provide fewer guarantees and are more cumbersome to manage.

5. Reporting, BI, and data warehousing

If your reporting layer runs on the same SQL instance as the ERP database (a deliberate choice because of licensing costs), you run into two Standard limitations: limited columnstore functionality and parallelism caps. In Enterprise, aggregate pushdown, string predicate pushdown, and SIMD optimizations are available, significantly accelerating BI queries at data warehouse scale. If your BI runs on a separate data warehouse, you can consider Standard for the ERP and a separate Developer edition for a BI development environment.

6. Virtualization and consolidation

Standard is licensed per core per physical or virtual machine running SQL. Each virtual SQL instance requires a separate set of core licenses with a minimum of 4 cores. Enterprise with Software Assurance offers unlimited virtualization rights per host: you license all cores on the host and can then run an unlimited number of SQL instances on it. For datacenters with many SQL instances on one or a few hosts, Enterprise therefore becomes cheaper than Standard, despite the higher price per core.

Source: Microsoft SQL Server Licensing Guide.

Which edition fits which ERP scenario?

Four typical scenarios make up the vast majority of ERP practice. For each scenario below, you can see which edition is the right choice in most cases.

SMB ERP up to 50 concurrent users: Standard

A Business Central installation with 20 to 50 users on one application server and one SQL server, database size under 200 GB, daily backup procedures, and an RTO of several hours. A Standard license with 4 to 8 cores is sufficient. The basic availability group feature provides enough protection against server failure without the Enterprise premium.

Mid-sized ERP with 50 to 250 users: Standard (with HA)

AFAS Profit, Exact Globe, or Unit4 Agresso with 150 users, a database of around 500 GB, and a synchronous HA setup with one secondary. SQL Server 2025 Standard with 16 cores and 128 to 256 GB RAM more than covers this. Reserve budget for two SQL licenses (primary + secondary) or use passive server rights with Software Assurance.

Enterprise ERP with 24/7 uptime and compliance: Enterprise

A Microsoft Dynamics 365 Finance & Operations on-premise deployment, 500+ users spread across multiple time zones, a 2 TB database with annual growth of 400 GB, GDPR-mandated TDE, and a DR site in a second datacenter. Enterprise is unavoidable here. The combination of TDE, partitioning for size management, multiple readable replicas, and online index rebuilds (which enable 24/7 maintenance without user impact) justifies the additional cost. See our article on the key differences between SQL Server Standard and Enterprise for an exhaustive feature comparison.

Virtualization datacenter with multiple ERP instances: Enterprise with SA

Hosters, MSPs, and enterprise IT departments running 10 or more SQL instances on a virtualized cluster almost always reach the break-even point of Enterprise + Software Assurance versus separate Standard licenses per VM. Unlimited virtualization rights fundamentally change the licensing economics.

Common mistakes when choosing an edition

In practice, we repeatedly see three mistakes in new ERP projects.

• Assuming current user numbers without a growth buffer. An ERP is usually used for 5 to 10 years; plan based on expected volumes in year 5.
• Using Developer edition in production. Developer is free but, from a licensing perspective, is allowed only for non-production purposes. Using it for a production ERP is an audit risk.
• Choosing Enterprise out of habit without a feature analysis. With the core and RAM expansion in SQL Server 2025 Standard (32 cores, 256 GB RAM), many workloads that previously required Enterprise can now run on Standard. Verify whether the Enterprise-specific features are actually being used.

Frequently asked questions

Can I use SQL Server Express for a production ERP environment?

Technically, it is possible for very small installations (fewer than 10 users, database under 50 GB), but in practice it is not recommended. Express does not support high availability, has only a 1.4 GB buffer pool, and does not offer SQL Server Agent for scheduled backups and maintenance jobs. Microsoft itself also explicitly recommends Express for Business Central only for dev/test.

Is SQL Server 2025 Standard powerful enough for Business Central?

For virtually all Business Central installations up to several hundred users, Standard is sufficient. The expansion to 32 cores and 256 GB RAM in SQL Server 2025 more than covers the requirements of Business Central environments in the SMB and midmarket segment. Only in the case of heavy customizations, large data volumes (more than 1 TB), or complex HA topologies is Enterprise recommended.

Do I need to choose Enterprise because of GDPR?

Not automatically. GDPR requires appropriate technical and organizational measures, but it does not prescribe a specific encryption implementation. Volume-level encryption (BitLocker) or column encryption on Standard can be sufficient if supported by a rationale and risk analysis. For organizations subject to NIS2, DORA, or NEN 7510, however, TDE is often the most pragmatic route, and therefore Enterprise.

What does the difference between Standard and Enterprise cost in practice?

The list price of Enterprise is roughly four times that of Standard per core. For an 8-core configuration, you are talking about a difference of roughly tens of thousands of euros with new licenses. With pre-owned licenses, both options move in the same proportion; the absolute saving on the new price is up to 70% there (50% for SQL Server 2025). Request a tailored quote for your specific core count.

Can I upgrade from Standard to Enterprise if I need more later?

Yes, an upgrade is technically straightforward via SQL Server Setup (Edition Upgrade). From a licensing perspective, you purchase additional Enterprise licenses; the previously purchased Standard licenses are not transferable as trade-in. That makes correctly estimating the requirement in advance financially relevant. A pragmatic middle ground is a Standard license for the production ERP combined with a pre-owned Enterprise license for a later migration when the need arises.